Method and Devices for Multiple Transmit Receive Point Cooperation for Reliable Communication

ABSTRACT

Embodiments of the present application pertain to control information for scheduling a transmission resource for downlink and uplink communications between one or more TRP and one or more UE. One Physical Downlink Control Channel (PDCCH) for DL control information transmission is assumed to carry at least one assignment or scheduling information block for at least one Physical Downlink Shared Channel (PDSCH) for DL data transmission or for at least one Physical Uplink Shared Channel (PUSCH) for UL data transmission. Embodiments of the present application provide methods of providing configuration information that can be used by a user equipment (UE) to determine transmission mode for the PDSCH and PUSCH as well as information to determine where to monitor for the PDSCH, PUSCH and PUCCH information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/646,050, filed Dec. 27, 2021, entitled “Method and Devices forMultiple Transmit Receive Point Cooperation for Reliable Communication,”which is a continuation of U.S. patent application Ser. No. 16/682,822,filed Nov. 13, 2019, now U.S. Pat. No. 11,212,825 issued on Dec. 28,2021, entitled “Method and Devices for Multiple Transmit Receive PointCooperation for Reliable Communication,” which is a continuation of PCTApplication No. PCT/CN2018/091326, entitled “Method And Devices ForMultiple Transmit Receive Point Cooperation For Reliable Communication,”filed on Jun. 14, 2018, which claims the benefit of U.S. ProvisionalApplication No. 62/520,510, filed on Jun. 15, 2017 and entitled “MethodAnd Devices For Multiple Transmit Receive Point Cooperation For ReliableCommunication,” and U.S. Provisional Application No. 62/568,757 filed onOct. 5, 2017 and entitled “Method and devices for multiple TransmitReceive Point Cooperation for Reliable communication.” Each of theseapplications is incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to wireless communications, andin particular embodiments, to systems and methods for multiple transmitreceive point (TRP) communication for reliable communication, includingsupporting multiple assignments of a single data channel type (unicastor UE-specific) within a single cell and multiple assignments of asingle data channel type (unicast or UE-specific) from multiple cells.

BACKGROUND

In traditional cellular networks, each transmit/receive point (TRP) isassociated with a coverage area or a traditional TRP-based cell and isassigned a traditional cell identifier (ID) to define the controlchannel and data channel so that simultaneous TRP to user equipment (UE)or UE to TRP communications can be supported for each traditional cell.The network may maintain the association between serving TRP and the UEthrough assigned traditional cell ID until a handover is triggered.

As the demand on mobile broadband increases, traditional cellularnetworks are deployed more densely and heterogeneously with a greaternumber of TRPs. In some implementations multiple TRPs may be serving asame UE.

Each TRP can transmit an assignment of resources that it will be usedwhen transmitting to the UE or receiving from the UE. For example, a TRPcan transmit information on a downlink control channel indicating to theUE where in a downlink shared channel data may be located for the UE.The number of TRPs that the UE is interacting with, or that is providingthe UE with information at any given time, may or may not be known tothe UE. In some scenarios, the number of TRPs, and more specifically thenumber of assignments, that a UE may need to monitor for may beexplicitly designated to the UE by the network. In other scenarios, thenumber of assignments for the UE may not be explicitly designated. Itwould be advantageous for the UE to be able to reduce the amount ofmonitoring of the downlink control channel, or other relevant channeltypes, that needs to be performed if the UE is unsure what assignmentsare for the UE to at least the amount of processing, and which forexample can ultimately affect the battery life of the UE.

SUMMARY

According to one aspect of the present disclosure there is provided amethod that involves: a user equipment (UE) receiving a configuration tomonitor more than one physical downlink control channel (PDCCH) forscheduling more than one physical downlink shared channel (PDSCH) orphysical uplink shared channel (PUSCH), or both, from one physical cellwithin one monitoring occasion wherein more than one PDSCH or PUSCH isassociated with one data channel type and one radio Network TemporaryIdentifier (RNTI) type; monitoring more than one PDCCH based on theconfiguration; and receiving more than one PDSCH or transmitting morethan one PUSCH simultaneously.

According to one aspect of the present disclosure there is provided amethod that involves configuring a user equipment (UE) with anassociation between at least one physical downlink control channel(PDCCH) and another property and configuring the UE to monitor at leastone PDCCH for at least one PDSCH or at least one PUSCH, or both, for onedata channel type and one RNTI type for one cell within one monitoringoccasion.

In some embodiments, configuring the UE to monitor the at least onePDCCH comprises providing the number of PDCCH explicitly to the UE byradio resource control (RRC) signaling or media access control controlelement (MAC-CE) signaling.

In some embodiments, at least one PDCCH can be associated with at leastone PDSCH and/or at least one PUSCH and one PDCCH is associated with onePDSCH or PUSCH.

In some embodiments, configuring the UE to monitor the at least onePDCCH comprises the UE determining the number of PDCCH to be monitoredimplicitly based on the configured association between the at least onePDCCH and the another property.

In some embodiments, the another property is one or more of: a controlresource set (CORESET) group associated with a UE-specific search space;a quasi-co-location (QCL) association between a demodulation referencesignal (DMRS) of the PDCCH and a downlink reference signal (DL RS); ahigh-layer sublayer; a HARQ entity; a cell radio network temporaryidentifier (C-RNTI); another configurable UE-specific ID; and a DMRSconfiguration for PDCCH monitoring.

In some embodiments, determining the number implicitly comprises usingthe number of PDCCH that is the same as the number of configured atleast one CORESET group.

In some embodiments, the method may further comprise: configuring the UEwith at least two different control resource sets (CORESET) and searchspace configurations according to different numbers of PDCCHs, wherein afirst CORESET and search space configuration for a first number ofPDCCHs and a second CORESET and search space configuration for a secondnumber of PDCCHs, wherein one search space configuration is based on oneor more aggregation level and one or more candidate number for eachaggregation level.

In some embodiments, determining the number implicitly comprises usingthe number of PDCCH that is the same as the number of configured atleast one QCL association between demodulation reference signal (DMRS)of PDCCH and a downlink reference signal (DL RS).

In some embodiments, the method may further comprise: configuring theassociation between the at least one PDCCH and at least one QCLassociation configuration wherein one PDCCH of the at least one PDCCH isassociated with one specific QCL association; monitoring the one PDCCHwith a specific QCL association with specific QCL configuration index;and determining the identity of the one PDCCH as the associated specificQCL configuration index.

In some embodiments, determining the number implicitly comprises usingthe number of PDCCH that is the same as the number of configured atleast one HARQ entity.

In some embodiments, the method may further comprise: configuring theassociation between at least one PDCCH and at least one HARQ entity,wherein one PDCCH of the at least one PDCCH is associated with onespecific HARQ entity with a specific HARQ entity index; and determiningthe identity of the one PDCCH as the associated HARQ entity index.

In some embodiments, determining the number implicitly comprises usingthe number of PDCCH that is the same as a total number of C-RNTI and/oranother configurable UE-specific ID.

In some embodiments, the method may further comprise: configuring theassociation between at least one PDCCH and at least one C-RNTI and/oranother configurable UE-specific ID, wherein one PDCCH of the at leastone PDCCH is associated with one specific C-RNTI and/or anotherconfigurable UE-specific ID with a specific index; monitoring the onePDCCH with the specific C-RNTI and/or another configurable UE-specificID; and determining the identity of the one PDCCH as an associatedspecific index for C-RNTI and/or another configurable UE-specific ID.

In some embodiments, the configuring comprises configuring the UE withat least two different control resource sets (CORESET), each associatedwith a UE-specific search space.

In some embodiments, different control resource sets are configured witha same one or more aggregation level and for each aggregation level ofdifferent control resource set the associated non-zero number ofcandidate can be same or different for same or different CORESET size.

In some embodiments, the method may further comprise providing the UEwith an association between a UL close-loop transmission power command(TPC) for at least one PUSCH/PUCCH and at least one PDCCH based on radioresource control (RRC) signaling.

In some embodiments, the one PUSCH/PUCCH uses TPC from one specificPDCCH that is also associated with the PUSCH/PUCCH.

In some embodiments, the one PUSCH/PUCCH uses TPC from one referencePDCCH that is configured as one of multiple PDCCHs.

In some embodiments, the method may further comprise providing the UEwith an association between at least one SRS trigger for SRStransmission and at least one PDCCH based on radio resource control(RRC) signaling.

In some embodiments, the UE use one SRS trigger from one specific PDCCHwhich is also associated with the specific SRS configuration.

In some embodiments, the UE uses one SRS trigger from one referencePDCCH which is configured as one of multiple PDCCHs.

In some embodiments, the UE is configured with at least two differentmaximum HARQ process numbers for PUSCH or PDSCH according to theconfigured number of PDCCH.

In some embodiments, the UE is configured to use a first maximum HARQprocess number for PUSCH or PDSCH which is associated with the firstnumber of PDCCH and use a second maximum HARQ process number for PUSCHor PDSCH which is associated with the second number of PDCCH.

In some embodiments, the first and second maximum HARQ process numbersare RRC configured or first and/or second maximum HARQ process numbersare determined by the number N of PDCCH and one predefined or configuredmaximum HARQ process number Nmax based on the form Nmax*N.

According to another aspect of the present disclosure there is providedmethod involving a first transmit receive point (TRP) transmitting afirst transmission on a dynamically scheduled resource and in a sametime resource block, a second TRP transmitting a second transmission ona configured resource.

According to another aspect of the present disclosure there is provideda method involving a first transmit receive point (TRP) transmitting afirst transmission over a first time-frequency resource and a second TRPdynamically scheduling transmission for duplicated data over a secondtime-frequency resource.

According to another aspect of the present disclosure there is provideda method involving a central scheduler scheduling an initialtransmission and one or more re-transmissions from at least two transmitreceive points (TRP), wherein each of the at least two TRP transmits atleast one of the initial transmission and the one or morere-transmissions.

According to another aspect of the present disclosure there is provideda method involving a first transmit receive point (TRP) scheduling aninitial transmission and one or more re-transmissions from the first TRPand at least one second TRP and the first TRP transmitting schedulinginformation to the at least one second TRP.

According to another aspect of the present disclosure there is provideda method involving a first transmit receive point (TRP) scheduling aninitial transmission and one or more re-transmissions from the first TRPand at least one second TRP, the first TRP transmitting schedulinginformation to the at least one second TRP and the at least one secondTRP scheduling at least one re-transmission from the at least one secondTRP.

According to another aspect of the present disclosure there is provideda method involving scheduling at least two uplink control channels fortransmission of the same data, the data on each channel of the at leasttwo channels having the same hybrid automatic request (HARQ) processidentifier (ID).

According to another aspect of the present disclosure there is provideda method involving scheduling at least two uplink control channels fortransmission of different data, the data on each channel of the at leasttwo channels having the same hybrid automatic request (HARQ) processidentifier (ID).

According to an aspect of the disclosure there is provided a method thatinvolves receiving a signaling including a transmission modeconfiguration for two or more Physical Downlink Control Channels(PDCCHs) and determining a transmission mode for the two or morePhysical Downlink Control Channels (PDCCHs) based on the transmissionmode configuration.

In some embodiments, wherein the transmission mode configuration iscommon for two or more PDCCHs.

In some embodiments, the transmission mode is predefined.

In some embodiments, the transmission mode configuration indicates arespective transmission mode for each of the two or more PDCCHs.

In some embodiments, wherein the transmission mode is different for eachof the at least one PDCCH for Physical Downlink Shared Channel (PDSCH)or Physical Uplink Shared Channel (PUSCH).

In some embodiments, the transmission mode configuration is signaledusing at least one of Radio Resource Control (RRC) signaling, DownlinkControl Information (DCI), Media Access Control Control Element (MACCE).

According to an aspect of the disclosure there is provided a methodinvolves receiving a signaling including at least one Control ResourceSet (CORESET) configuration and monitoring one or more Physical DownlinkControl Channels (PDCCH) in at least one CORESET within a monitoringoccasion based on the at least one CORESET configuration, wherein eachCORESET configuration has at least one PDCCH identifier used to indicatea number of PDCCH and an association between a PDCCH and a CORESET.

In some embodiments, one PDCCH identifier includes one PDCCH identifierwhich is common for Physical Downlink Shared Channel (PDSCH) andPhysical Uplink Shared Channel (PUSCH).

In some embodiments, one PDCCH identifier includes one PDCCH identifierset including one specific PDCCH identifier for PDSCH and one specificPDCCH identifier for PUSCH.

In some embodiments, at least one PDCCH identifier of each CORESETconfiguration refers to M PDCCH identifiers, where M is an integer ≥1,and each of the M PDCCH identifiers is used to indicate whether aparticular PDCCH of the maximum M PDDCH is monitored or is not monitoredin the CORESET.

In some embodiments, each of the M PDCCH is associated with one specificPDCCH identifier of the M PDCCH identifiers.

In some embodiments, each of the M PDCCH is indicated to be monitored,or not, based on the value of the associated PDCCH identifier configuredfor each CORESET.

In some embodiments, the value of the associated PDCCH identifier is setas any one of: 0/1; on/off; or true/false.

In some embodiments, each of the M PDCCH is indicated to be monitored inall configured CORESET.

In some embodiments, the value of PDCCH identifier associated with thespecific PDCCH is any one of: 1; on or true.

In some embodiments, a number P of PDCCH which needs to be monitored inone monitoring occasion equals to the total number of different PDCCHwhich is configured to be monitored in at least one CORESET.

In some embodiments, the at least one associated PDCCH identifier ofeach CORESET configuration is a single PDCCH identifier that indicatesthat a single PDCCH associated with a specific value of the single PDCCHidentifier is to be monitored in the CORESET.

In some embodiments, a single PDCCH identifier of each CORESETconfiguration is configured with one specific value out of M differentvalues, where M is an integer ≥1, which are used to indicate the maximumM PDCCH that may be monitored in at least one CORESET configured for onesearch space type.

In some embodiments, each of the M PDCCH is associated with one specificvalue of the single PDCCH identifier.

In some embodiments, M different values of the single PDCCH identifierare 1, . . . , M.

In some embodiments, each of the M PDCCH is indicated to be monitored inat least one CORESET which has the PDCCH identifier value associated forthe specific PDCCH; otherwise, the PDCCH is not monitored.

In some embodiments, a number P of PDCCH to be monitored in onemonitoring occasion equals a total number of different PDCCH which areconfigured to be monitored from at least one CORESET.

In some embodiments, the single PDCCH identifier includes one PDCCHidentifier which is common for Physical Downlink Shared Channel (PDSCH)and Physical Uplink Shared Channel (PUSCH).

In some embodiments, the single PDCCH identifier includes a PDCCHidentifier set including a specific PDCCH identifier for PDSCH and aspecific PDCCH identifier for PUSCH.

According to an aspect of the disclosure there is provided a methodinvolving receiving a signaling including a Physical Downlink ControlChannel (PDCCH) number (PDCCHNum, PDCCHNum≥1) configuration; determiningan association between the PDCCH number and at least one ControlResource Set (CORESET); and monitoring a number of PDCCH equal to thePDCCH number in at least one CORESET within a monitoring occasion basedon the association.

In some embodiments, determining the association between the PDCCHnumber and the at least one CORESET further involves: receiving at leastone CORESET configuration; wherein each CORESET configuration of the atleast one CORESET has at least one PDCCH identifier used to indicate anassociated PDCCH to be monitored or not in the CORESET.

In some embodiments, at least one PDCCH identifier of each CORESETconfiguration refers to a number of PDCCH identifiers equal to the PDCCHnumber that is used to indicate an associated PDCCH to be monitored, ornot, in the CORESET.

In some embodiments, at least one PDCCH identifier of each CORESETconfiguration refers to a single PDCCH identifier which may beconfigured with one value out of the PDCCH number of different valuesused to indicate an associated PDCCH to be monitored, or not, in theCORESET.

In some embodiments, determining the association between the PDCCHnumber and the at least one CORESET further involves predefining anassociation between PDCCH and CORESET with a specific PDCCH number and aspecific CORESET number.

In some embodiments, predefining an association rule between PDCCH andCORESET based on at least one of: all CORESET may be split intonon-overlapping P CORESET sets wherein each CORESET set with specificindex p (p=1, . . . P) has at least one CORESET and at least two CORESETfrom different CORESET set have continuous CORESET index and/or CORESETconfiguration index; and each PDCCH with specific PDCCH identifier(PDCCHIdx=p (p=1, . . . P)) is associated with specific COREST set pwherein P equals to PDCCH number PDCCHNum.

In some embodiments, predefining the association further involvespredefining an association table between PDCCH and CORESET with thePDCCH number and the CORESET number based on the CORESET configuration.

In some embodiments, for up to two PDCCH and up to three CORESET, themapping table includes at least one of the following relationships:

PDCCHNum CORESET Number Association 1 1 PDCCH1-CORESET0 1 2PDCCH1-CORESET0 PDCCH1-CORESET1 2 2 PDCCH1-CORESET0 PDCCH2-CORESET1 2 3PDCCH1-CORESET0 PDCCH1-CORESET1 PDCCH2-CORESET2 Or PDCCH1-CORESET0PDCCH2-CORESET1 PDCCH2-CORESET2

In some embodiments, in the table above, PDCCHNum=1 indicates inmonitoring one PDCCH for PDSCH or one PDCCH for PUSCH, or both, in one,or multiple, CORESET; and PDCCHNum=2, indicates in monitoring two PDCCHsfor PDSCH or two PDCCH for PUSCH, or both, in multiple CORESET anddifferent PDCCH are monitored from different CORESET.

In some embodiments, PDCCHNum includes one PDCCHNum which is common forPDSCH and PUSCH.

In some embodiments, PDCCHNum includes one PDCCHNum set including onespecific PDCCH number for PDSCH and one PDCCH number for PUSCH.

According to an aspect of the disclosure there is provided a methodinvolving: receiving a signaling including a Physical Downlink ControlChannel (PDCCH) number (PDCCHNum, PDCCHNum ≥1) configuration; receivingan indication for determining the PDCCH monitoring mode; and monitoringa number of PDCCH equal to the PDCCH number in at least one ControlResource Set (CORESET) within a monitoring occasion.

In some embodiments, the PDCCH monitoring mode comprises one of a firstPDDCH monitoring mode that corresponds to monitoring different PDCCH indifferent CORESET for at least two PDCCH for PUSCH or at least two PDCCHfor PUSCH based on a predefined association between PDCCH and CORESET ora second PDDCH monitoring mode corresponds to monitoring one, ormultiple, PDCCH in all CORESET that are configured for one search spacetype.

In some embodiments, the predefined association includes one of apredefined association rule between PDCCH and CORESET or a predefinedassociation table between PDCCH and CORESET.

In some embodiments, for up to two PDCCH and up to three CORESET, thepredefined association table includes at least one of the followingrelationships

PDCCHDLNum or PDCCHULNum (for configured PDSCH CORESET or PUSCH) NumberAssociation 2 2 PDCCH1-CORESET1 PDCCH2-CORESET2 2 3 PDCCH1-CORESET1PDCCH1-CORESET2 PDCCH2-CORESET3 Or PDCCH1-CORESET1 PDCCH2-CORESET2PDCCH2-CORESET3

In some embodiments, the method, further involves, if the indicationindicates a first PDDCH monitoring mode is to be used, the first PDDCHmonitoring mode is used, otherwise a second PDDCH monitoring mode isused.

According to an aspect of the disclosure there is provided a methodinvolving determining an initialization value for generating ascrambling sequence used to scramble a physical channel based on anassociated Physical Downlink Control Channel (PDCCH) identity.

In some embodiments, the associated PDCCH identity is a PDCCH index.

In some embodiments, the physical channel is at least one of a PDCCH, aPhysical Downlink Shared Channel (PDSCH), and a Physical Uplink SharedChannel (PUSCH).

In some embodiments, the method further involves determining aninitialization value for scrambling a first physical channel which isassociated with a first PDCCH identity and determining an initializationvalue for scrambling a second physical channel which is associated witha second PDCCH identity.

According to an aspect of the disclosure there is provided a methodinvolving receiving multiple Physical Downlink Control Channels (PDCCHs)or Physical Downlink Shared Channel (PDSCHs), or both; and transmittinga single Physical Uplink Control Channel (PUCCH) for the transmission ofa combination of multiple uplink control information (UCI) feedback,wherein each UCI feedback is associated with at least one of onespecific PDCCH and one specific PDSCH.

According to an aspect of the disclosure there is provided a methodinvolving receiving multiple respective Physical Downlink ControlChannels (PDCCHs) or Physical Downlink Shared Channels (PDSCHs), orboth; and transmitting multiple Physical Uplink Control Channels(PUCCHs) for the transmission of multiple uplink control information(UCI) feedback, wherein each UCI feedback is associated with at leastone of one specific PDCCH and one specific PDSCH.

In some embodiments, the methods may further involve determining thesingle or multiple PUCCH resources.

In some embodiments, the single or multiple PUCCH resources include atleast one of: a time resource; a frequency resource; a code or sequenceresource; a frequency hopping pattern; a transmission beam; and PUCCHformat.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH use the same or differentPUCCH format.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH are located in a single slot,such that each PUCCH's starting OFDM symbol is located in a single slotand its duration is less than or equal to the duration of a slot.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH are located in multiple slots,such that each PUCCH's starting OFDM symbol is located in a single slotand its duration is less than, equal to, or longer than, the duration ofa slot.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH are located in multiple slots,such that each PUCCH's ending OFDM symbol is located in a single slotand its duration is less than, equal to, or longer than, the duration ofa slot.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH are located in separate slots,such that each PUCCH's starting OFDM symbol is located in a given slotand its duration is less than or equal to the duration of a slot.

In some embodiments, wherein the multiple PUCCH resources used for thetransmission of multiple respective PUCCH use respective transmissionbeams that are derived using the quasi-collocated association between arespective PUCCH Demodulation Reference Signal (DMRS) and a respectiveDownlink Reference Signal (DL RS).

In some embodiments, the DL RS is a Channel State Information—ReferenceSignal (CSI-RS).

In some embodiments, the DL RS is a PDCCH DMRS.

In some embodiments, the DL RS is a PDSCH DMRS.

In some embodiments, resource information pertaining to the single ormultiple PUCCH resource is configured with at least one of: RRCsignaling; Downlink Control Information (DCI); Media Control AccessControl Element (MAC CE); and a predefined rule.

In some embodiments, the methods involve determining a PUCCH feedbackmode; and transmitting a single or multiple PUCCH based on the PUCCHfeedback mode.

In some embodiments, the determining the PUCCH feedback mode is made byselecting one of two separate feedback modes.

In some embodiments, a first mode is for a single PUCCH and a secondmode is for multiple PUCCH.

In some embodiments, determining the PUCCH feedback mode comprisesmaking a determination based on an implicit mechanism using a PDCCH toCORESET association.

In some embodiments, determining the PUCCH feedback mode comprisesreceiving a higher-layer signaling.

In some embodiments, the higher-layer signaling at least one of RRCsignaling, Downlink Control Information (DCI), and Media Control AccessControl Element (MAC CE).

According to an aspect of the disclosure there is provided a methodinvolving determining an association between multiple Channel StateInformation—Reference Signal (CSI-RS) configurations and multiplePhysical Uplink Shared Channels (PUSCHs); and reporting one or multipleCSI-RS measurement over an associated separate PUSCH based on theassociation between multiple CSI-RS configuration and multiple PUSCHs.

In some embodiments, determining the association comprises receiving asignaling indicating the association.

In some embodiments, determining the association involves determining aCSI-RS configuration that is associated with a PUSCH which is scheduledby a PDCCH, the PDCCH being associated with a DMRS quasi co-located witha CSI-RS.

According to some embodiments of the disclosure, there is provided adevice including a processor and a computer-readable medium. Thecomputer-readable medium having stored thereon computer executableinstructions, that when executed by the processor perform one or more ofthe various methods described above or detailed below.

In some embodiments, the device may be an electronic device, such as auser equipment.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present embodiments, and theadvantages thereof, reference is now made, by way of example, to thefollowing descriptions taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 illustrates an example communication system in which embodimentsof the present disclosure could be implemented;

FIG. 2 illustrates two neighboring NR cells of an example communicationsystem in which embodiments of the present disclosure could beimplemented;

FIGS. 3A and 3B illustrate example devices that may implement themethods and teachings according to this disclosure;

FIG. 4A is a representative illustration of a Physical Downlink ControlChannel (PDCCH) and a Physical Downlink Shared Channel (PDSCH)communication between a transmit receive point (TRP) and a userequipment in a cell;

FIG. 4B is a representative illustration of PDCCH and PDSCHcommunications between two TRPs and a single user equipment in a cell;

FIG. 5 is a table showing two examples of potential associations betweentwo PDCCH assignments and other parameters;

FIGS. 6A and 6B illustrate associations between transmission modeconfiguration used for one or more PDCCH;

FIGS. 7A to 7E illustrate examples of associations between PDCCH,Control Resource Sets (CORESET) and PDCCH identifiers, where a number ofPDCCH is equal to 2, which can be used for configuring user equipment(UE) with a common configuration;

FIGS. 8A to 8E illustrate examples of associations between PDCCH,CORESET and PDCCH identifiers, wherein the number of PDCCH is equal toM, which can be used for configuring UE with a common configuration;

FIG. 9 is a flow chart describing operation of a network that includesconfiguring the UE to monitor the appropriate PDUCCH;

FIGS. 10A to 10C illustrate examples of associations between PDCCH,CORESET and PDCCH identifiers, wherein the number of downlink (DL) anduplink (UL) PDCCH is equal to M, which can be used for configuring UEwith a common configuration;

FIGS. 11A to 11D illustrate examples of associations between PDCCH,CORESET and PDCCH identifiers, wherein the number of DL and UL PDCCH isequal to M, which can be used for configuring UE with a commonconfiguration;

FIGS. 12A to 12C illustrate examples of associations between PDCCH,CORESET and PDCCH identifiers, wherein the number of PDCCH is equal to2, which can be used for configuring UE with a common configuration;

FIG. 12D is a flow chart describing operation of a network that includesconfiguring the UE to monitor the appropriate PDUCCH;

FIGS. 13A and 13B illustrate examples of associations between PDCCH,CORESET and PDCCH identifiers, wherein the number of DL and UL PDCCH isequal to 2, which can be used for configuring UE with a commonconfiguration;

FIG. 14 is an illustration of a portion of a network including twotransmit-receive points (TRP) and a UE and the transmission beams thatare used for communication between the TRPs and UE for at least PDCCHand PUCCH;

FIGS. 15A to 15F illustrate examples of resource configurations used bya UE for separate PUCCH to respective TRPs;

FIGS. 16A and 16B illustrate example associations between one or morerespective channel state information (CSI) and PUSCH;

FIG. 17 is a flow chart describing a method according to an aspect ofthe disclosure;

FIG. 18 is a flow chart describing a method according to another aspectof the disclosure;

FIG. 19 is a flow chart describing a method according to a furtheraspect of the disclosure;

FIG. 20 is a flow chart describing a method according to yet anotheraspect of the disclosure;

FIG. 21 is a flow chart describing a method according to still anotheraspect of the disclosure;

FIG. 22 is a flow chart describing a method according to yet a furtheraspect of the disclosure;

FIG. 23 is a flow chart describing a method according to yet a furtheraspect of the disclosure;

FIG. 24A is a representative illustration of downlink and uplinkassignments between multiple TRPs and various UEs in a single cell;

FIG. 24B is a representative illustration of an assignment oftransmission resources for downlink and uplink communications formultiple TRPs in a single cell;

FIG. 25A is a representative illustration of two PDCCH and associatedPDSCH having different time unit segments;

FIG. 25B is a representative illustration of two PDCCH and associatedPDSCH having the same respective time unit segments;

FIG. 26A is a representative drawing of a common PUCCH associated withtwo PDCCH and PDSCH;

FIG. 26B is a representative drawing of a two PUCCH, each associatedwith a respective PDCCH and PDSCH;

FIG. 26C is a representative drawing of a common Uplink ControlInformation (UCI) associated with two PDCCH piggybacked on top of aPUSCH;

FIG. 26D is a representative drawing of two UCIs associated with one oftwo possible PDCCH piggybacked on top of one out of two possible PUSCH;

FIG. 26E is a representative drawing of one PUCCH associated to one oftwo possible PDCCH and one UCI associated with one of two possible PDCCHpiggybacked on top of one of two possible PUSCH;

FIG. 26F is a representative drawing of a common PUCCH associated withtwo PDCCH and a single common PUSCH associated with one of two possiblePDCCH;

FIG. 26G is a representative drawing of two PUCCHs, each associated witha respective PDCCH, and separate PUSCH, each associated with arespective PDCCH;

FIG. 27 is a representative illustration of a portion of a transmissionresource that has been sub-divided in different ways based on assignmentidentity, codeword or codeblock;

FIG. 28A is a representative drawing of a PUSCH associated with aparticular one of two possible PDCCH;

FIG. 28B is a representative drawing of a Sounding Reference Signal(SRS) associated with a particular one of two possible PDCCH;

FIG. 28C is a representative drawing of two Sounding Reference Signals(SRS) associated with a particular one of two possible PDCCH;

FIG. 29A is a representation of HARQ process numbers for a singleassignment for a single data channel;

FIG. 29B is a representation of HARQ process numbers for a multipleassignments for a single data channel;

FIG. 30A is a schematic diagram illustrating centralized scheduling forTRP cooperation;

FIG. 30B is a schematic diagram illustrating independent scheduling forTRP cooperation;

FIG. 31A is a schematic diagram illustrating TRP cooperation using dualconnectivity (DC);

FIG. 31B is a representation of multiple transmission resources over aduration of time during which a handover from one cell to anotheroccurs;

FIG. 32A is a schematic diagram illustrating how repetition of duplicatetransmissions may occur in a centralized scheduling scenario for TRPcooperation;

FIG. 32B is a schematic diagram illustrating how repetition of duplicatetransmissions may occur in an independent scheduling scenario for TRPcooperation;

FIG. 33 is a representation of multiple transmission resources over aduration of time illustrating how repetition of transmissions may occurfor TRP cooperation in an independent scheduling scenario;

FIG. 34A is a representation of multiple transmission resources over aduration of time illustrating NR-PDCCH transmission for PDSCHrepetitions;

FIG. 34B is another representation of multiple transmission resourcesover a duration of time illustrating NR-PDCCH transmission for PDSCHrepetitions

FIG. 35 is a representation of multiple transmission resources over aduration of time illustrating the relationship between PDCCH, an uplink(UL) PDCCH acknowledgement and an UL data ACK/NACK;

FIG. 36 is a representation of multiple transmission resources over aduration of time illustrating the relationship between PDCCH, and ULdata ACK/NACK in which retransmissions of PDCCH includes transmissionblock size (TBS) information; and

FIG. 37 is a representative illustration of primary downlink assignmentsand auxiliary downlink assignments between multiple TRPs and various UEsin a single cell.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Embodiments of the present application pertain to control informationfor scheduling a transmission resource for downlink and uplinkcommunications between one or more TRP and one or more UE. One PhysicalDownlink Control Channel (PDCCH) for DL control information transmissionis assumed to carry at least one assignment or scheduling informationblock for at least one Physical Downlink Shared Channel (PDSCH) for DLdata transmission or for at least one Physical Uplink Shared Channel(PUSCH) for UL data transmission. In some cases, a PDCCH is also knownas Downlink Control Information (DCI). Moreover, in someimplementations, one PDCCH can be associated with one HARQ process forone PDSCH or one PUSCH. The PDCCH for New Radio (NR), a next evolutionfor wireless communications, may be referred to as NR-PDCCH. The cellfor New Radio (NR) may be referred to as a NR-cell. The PDSCH for NewRadio (NR) may be referred to as a NR-PDSCH. The PUCCH for New Radio(NR) may be referred to as a NR-PUCCH. The PUSCH for New Radio (NR) maybe referred to as a NR-PUSCH. Generally, NR-PDCCH, NR-PDSCH, NR-PUSCH,NR-PUCCH are used for discussion within this application. Two antennaports are said to be quasi co-located (QCL) if the large-scaleproperties of the channel over which a symbol on one antenna port isconveyed can be inferred from the channel over which a symbol on theother antenna port is conveyed. The large-scale properties include oneor more of delay spread, Doppler spread, Doppler shift, average gain,average delay, and spatial Rx parameters. One control resource set(CORESET) group contains at least one CORESET. A CORESET is defined witha time (e.g. symbol/slot level)-frequency (e.g. PRB level) resource forPDCCH monitoring.

Table 1 below illustrates a relationship between two respective PDCCHand other characteristics associated with the respective PDCCH. PDCCH1may have an associated resource assignment (Assignments), an associateddownlink control information (DCI1), an associated PDSCH (PDSCH1) anassociated PUSCH (PUSCH1) and an associated hybrid automatic repeatrequest process (HARQ Process 1). Likewise, PDCCH2 may have anassociated resource assignment (Assignment2), an associated downlinkcontrol information (DCI2), an associated PDSCH (PDSCH2) an associatedPUSCH (PUSCH2) and an associated hybrid automatic repeat request process(HARQ Process 2). Each PDCCH does not necessarily include all of theassociations all of the time, but they are examples of characteristicsthe PDCCH may have associations with.

TABLE 1 A clarification for mapping between different terminologiesPDCCH1 Assignment1 DCI1 PDSCH1 PUSCH1 HARQ PROCESS 1 PDCCH2 Assignment2DCI2 PDSCH2 PUSCH2 HARQ PROCESS 2

FIG. 1 illustrates an example communication system 100 in whichembodiments of the present disclosure could be implemented. In general,the system 100 enables multiple wireless or wired elements tocommunicate data and other content. The purpose of the system 100 may beto provide content (voice, data, video, text) via broadcast, narrowcast,user device to user device, etc. The system 100 may operate efficientlyby sharing resources such as bandwidth.

In this example, the communication system 100 includes electronicdevices (ED) 110 a-110 c, radio access networks (RANs) 120 a-120 b, acore network 130, a public switched telephone network (PSTN) 140, theInternet 150, and other networks 160. While certain numbers of thesecomponents or elements are shown in FIG. 1 , any reasonable number ofthese components or elements may be included in the system 100.

The EDs 110 a-100 c are configured to operate, communicate, or both, inthe system 100. For example, the EDs 110 a-110 c are configured totransmit, receive, or both via wireless communication channels. Each ED110 a-100 c represents any suitable end user device for wirelessoperation and may include such devices (or may be referred to) as a userequipment/device (UE), wireless transmit/receive unit (WTRU), mobilestation, mobile subscriber unit, cellular telephone, station (STA),machine type communication device (MTC), personal digital assistant(PDA), smartphone, laptop, computer, touchpad, wireless sensor, orconsumer electronics device.

In FIG. 1 , the RANs 120 a-120 b include base stations 170 a-170 b,respectively. Each base station 170 a-170 b is configured to wirelesslyinterface with one or more of the EDs 110 a-110 c to enable access toany other base station 170 a-170 b, the core network 130, the PSTN 140,the Internet 150, and/or the other networks 160. For example, the basestations 170 a-170 b may include (or be) one or more of severalwell-known devices, such as a base transceiver station (BTS), a Node-B(NodeB), an evolved NodeB (eNodeB), a Home eNodeB, a gNodeB (sometimescalled a “gigabit” NodeB), a transmission point (TP), a transmit/receivepoint (TRP), a site controller, an access point (AP), or a wirelessrouter. When any of the example base stations listed above are describedbelow, it is assumed that they are interchangeable with other types ofbase stations. Any ED 110 a-110 c may be alternatively or jointlyconfigured to interface, access, or communicate with any other basestation 170 a-170 b, the internet 150, the core network 130, the PSTN140, the other networks 160, or any combination of the preceding.Optionally, the system may include RANs, such as RAN 120 b, wherein thecorresponding base station 170 b accesses the core network 130 via theinternet 150, as shown.

The EDs 110 a-110 c and base stations 170 a-170 b are examples ofcommunication equipment that can be configured to implement some or allof the functionality and/or embodiments described herein. In theembodiment shown in FIG. 1 , the base station 170 a forms part of theRAN 120 a, which may include other base stations, base stationcontroller(s) (BSC), radio network controller(s) (RNC), relay nodes,elements, and/or devices. Any base station 170 a, 170 b may be a singleelement, as shown, or multiple elements, distributed in thecorresponding RAN, or otherwise. Also, the base station 170 b forms partof the RAN 120 b, which may include other base stations, elements,and/or devices. Each base station 170 a-170 b may be configured tooperate to transmit and/or receive wireless signals within a particulargeographic region or area, sometimes referred to as a coverage area. Acell may be further divided into cell sectors, and a base station 170a-170 b may, for example, employ multiple transceivers to provideservice to multiple sectors. In some embodiments a base station 170a-170 b may be implemented as pico or femto nodes where the radio accesstechnology supports such. In some embodiments, multiple-inputmultiple-output (MIMO) technology may be employed having multipletransceivers for each coverage area. The number of RAN 120 a-120 b shownis exemplary only. Any number of RAN may be contemplated when devisingthe system 100.

The base stations 170 a-170 b communicate with one or more of the EDs110 a-110 c over one or more air interfaces 190 using wirelesscommunication links e.g. RF, Wave, IR, etc. The air interfaces 190 mayutilize any suitable radio access technology. For example, the system100 may implement one or more channel access methods, such as codedivision multiple access (CDMA), time division multiple access (TDMA),frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), orsingle-carrier FDMA (SC-FDMA) in the air interfaces 190.

A base station 170 a-170 b may implement Universal MobileTelecommunication System (UMTS) Terrestrial Radio Access (UTRA) toestablish an air interface 190 using wideband CDMA (WCDMA). In doing so,the base station 170 a-170 b may implement protocols such as HSPA, HSPA+optionally including HSDPA, HSUPA or both. Alternatively, a base station170 a-170 b may establish an air interface 190 with Evolved UTMSTerrestrial Radio Access (E-UTRA) using LTE, LTE-A, and/or LTE-B. It iscontemplated that the system 100 may use multiple channel accessfunctionality, including such schemes as described above. Other radiotechnologies for implementing air interfaces include IEEE 802.11,802.15, 802.16, CDMA2000, CDMA2000 1×, CDMA2000 EV-DO, IS-2000, IS-95,IS-856, GSM, EDGE, and GERAN. Of course, other multiple access schemesand wireless protocols may be utilized.

The RANs 120 a-120 b are in communication with the core network 130 toprovide the EDs 110 a-110 c with various services such as voice, data,and other services. Understandably, the RANs 120 a-120 b and/or the corenetwork 130 may be in direct or indirect communication with one or moreother RANs (not shown), which may or may not be directly served by corenetwork 130, and may or may not employ the same radio access technologyas RAN 120 a, RAN 120 b or both. The core network 130 may also serve asa gateway access between (i) the RANs 120 a-120 b or EDs 110 a-110 c orboth, and (ii) other networks (such as the PSTN 140, the Internet 150,and the other networks 160). In addition, some or all of the EDs 110a-110 c may include functionality for communicating with differentwireless networks over different wireless links using different wirelesstechnologies and/or protocols. PSTN 140 may include circuit switchedtelephone networks for providing plain old telephone service (POTS).Internet 150 may include a network of computers and subnets (intranets)or both, and incorporate protocols, such as IP, TCP and UDP. EDs 110a-110 c may be multimode devices capable of operation according tomultiple radio access technologies, and incorporate multipletransceivers necessary to support such.

It is contemplated that the communication system 100 as illustrated inFIG. 1 may support a New Radio (NR) cell, which also may be referred toas hyper cell. Each NR cell includes one or more TRPs using the same NRcell ID. The NR cell ID is a logical assignment to all physical TRPs ofthe NR cell and may be carried in a broadcast synchronization signal.The NR cell may be dynamically configured. The boundary of the NR cellmay be flexible and the system dynamically adds or removes TRPs to fromthe NR cell.

In one embodiment, a NR cell may have one or more TRPs within the NRcell transmitting a UE-specific data channel, which serves a UE. The oneor more TRPs associated with the UE specific data channel are also UEspecific and are transparent to the UE. Multiple parallel data channelswithin a single NR cell may be supported, each data channel serving adifferent UE.

In another embodiment, one or more TRPs within a NR cell may transmit aUE specific dedicated control channel, which serves a UE and carriesUE-specific control information associated with the UE.

In another embodiment, a broadcast common control channel and adedicated control channel may be supported. The broadcast common controlchannel may carry common system configuration information transmitted byall or partial TRPs sharing the same NR cell ID. Each UE can decodeinformation from the broadcast common control channel in accordance withinformation tied to the NR cell ID. One or more TRPs within a NR cellmay transmit a UE specific dedicated control channel, which serves a UEand carries UE-specific control information associated with the UE.Multiple parallel dedicated control channels within a single NR cell maybe supported, each dedicated control channel serving a different UE. Thedemodulation of each dedicated control channel may be performed inaccordance with a UE-specific reference signal (RS), the sequence and/orlocation of which are linked to the UE ID or other UE specificparameters.

In some embodiments, one or more of these channels, including thededicated control channels and the data channels, may be generated inaccordance with a UE specific parameter, such as a UE ID, and/or an NRcell ID. Further, the UE specific parameter and/or the NR cell ID can beused to differentiate transmissions of the data channels and controlchannels from different NR cells.

An ED, such as a UE, may access the communication system 100 through atleast one of the TRP within a NR cell using a UE dedicated connectionID, which allows one or more physical TRPs associated with the NR cellto be transparent to the UE. The UE dedicated connection ID is anidentifier that uniquely identifies the UE in the NR cell. For example,the UE dedicated connection ID may be identified by a sequence. In someimplementations, the UE dedicated connection ID is assigned to the UEafter an initial access. The UE dedicated connection ID, for example,may be linked to other sequences and randomizers which are used for PHYchannel generation.

In some embodiments, the UE dedicated connection ID remains the same aslong as the UE is communicating with a TRP within the NR cell. In someembodiments, the UE can keep original UE dedicated connection ID whencrossing NR cell boundary. For example, the UE can only change its UEdedicated connection ID after receiving signaling from the network.

It is obviously understood that any number of NR cells may beimplemented in the communication system 100. For example, FIG. 2illustrates two neighboring NR cells in an example communication system,in accordance with an embodiment of the present disclosure.

As illustrated in FIG. 2 , NR cells 282, 284 each include multiple TRPsthat are assigned the same NR cell ID. For example, NR cell 282 includesTRPs 286, 287, 288, 289, 290, and 292, where TRPs 290, 292 communicateswith an ED, such as UE 294. It is obviously understood that other TRPsin NR cell 282 may communicate with UE 294. NR cell 284 includes TRPs270, 272, 274, 276, 278, and 280. TRP 296 is assigned to NR cells 282,284 at different times, frequencies or spatial directions and the systemmay switch the NR cell ID for transmit point 296 between the two NRcells 282 and 284. It is contemplated that any number (including zero)of shared TRPs between NR cells may be implemented in the system.

In one embodiment, the system dynamically updates the NR cell topologyto adapt to changes in network topology, load distribution, and/or UEdistribution. In some implementations, if the concentration of UEsincreases in one region, the system may dynamically expand the NR cellto include TRPs near the higher concentration of UEs. For example, thesystem may expand NR cell to include other TRPs if the concentration ofUEs located at the edge of the NR cell increases above a certainthreshold. As another example, the system may expand NR cell to includea greater concentration of UEs located between two hyper cells. In someimplementations, if the traffic load increases significantly at oneregion, the system may also expand the NR cell associated with theregion to include TRPs for the increased traffic load. For example, ifthe traffic load of a portion of the network exceeds a predeterminedthreshold, the system may change the NR cell ID of one or more TRPs thatare transmitting to the impacted portion of the network.

In another embodiment, the system may change the NR cell ID associatedwith TRP 296 from the NR cell ID of NR cell 282 to the NR cell ID of NRcell 284. In one implementation, the system can change the associationof a TRP with different NR cells periodically, such as every 1millisecond. With such a flexible NR cell formation mechanism, all UEscan be served by the best TRPs so that virtually there are no cell edgeUEs.

In yet another embodiment, the shared TRP 296 can reduce interferencefor UEs located at the boundary between the two NR cells 282, 284. UEsthat are located near the boundaries of two NR cells 282, 284 experienceless handovers because the shared TRP is associated with either NR cellat different times, frequencies or spatial directions. Further, as a UEmoves between the NR cells 282, 284, the transition is a smootherexperience for the user. In one embodiment, the network changes the NRcell ID of the TRP 296 to transition a UE moving between NR cells 282,284. Moreover, the system may apply TRP selection techniques to minimizeintra-NR cell interference and inter-NR cell interference. In oneembodiment, a TRP sends a downlink channel state information(CSI)—reference symbol (RS). Some pilot (also known as reference signal)ports may be defined such that the UEs can measure the channel stateinformation and report it back to the network. A CSI-RS port is a pilotport defined as a set of known symbols from a sequence transmitted overknown resource elements (for example OFDM resource elements) for UEs tomeasure the channel state. A UE assigned to measure a particular CSI-RSport can measure the transmitted CSI-RS sequence, measure the associatedchannel state and report it back to the network. The network, such as acontroller, may select the best TRPs for all served UEs based on thedownlink measurements. In another embodiment, a TRP detects an uplinksounding reference signal (SRS) sequence from a UE in the configuredtime-frequency resources. For example, Constant Amplitude Zero AutoCorrelation (CAZAC) sequences such as ZC sequences can be used as basesequences for SRS. The TRP reports a measurement of the detected uplinkSRS sequence to the network, such as a controller. The controller thenselects the optimal TRPs for all served UEs based on the measurements.

A UE can monitor one or more control resource sets (CORESET) fordownlink control information. Long term Evolution (LTE) is known tosupport UE specific and/or case specific search space definitions. Atime/frequency resource set (i.e. control resource set) can be definedas a set of Resource Element Groups (REGs) under a given numerology. Insome implementations a REG is four consecutive Resource Elements (RE).An RE is a smallest transmission resource element, which may, forexample, be 1 symbol by 1 sub-carrier.

A search space for one search space type may be defined by at least someof the following properties: one or more aggregation levels (AL), anumber of decoding candidates (i.e. a candidate number (CN)) for eachaggregation level and a set of Control Channel Elements (CCEs) for eachdecoding candidate. A candidate is a location in the search space thatmay include downlink control information for the UE. Thus, a candidatenumber is a defined number of potential locations in the search space.In some implementations, a CCE may be nine consecutive REGs. Anaggregation level may be defined as 1, 2, 4, or 8 consecutive CCEs. Asan example, an aggregation level of 2 would be 2 consecutive CCEs.

Table 2 below illustrates an example of Enhanced PDCCH (EPDCCH) for twoexample CORESETs, and the specifically associated search space both theaggregation level and candidate number. The values in the CORESET A andCORESET B columns of Table 2 represent the number of Physical ResourceBlocks (PRB) used in the CORESET. The values of L=2 to L=32 are thedifferent aggregation levels. The two numbers in each aggregation levelcolumn represent the number of candidates for the PRB size of CORESET Aand CORESET B in a respective row. Where the number of candidates iszero, that particular aggregation level is not supported for thecorresponding CORESET.

TABLE 2 Number of candidates for different aggregation levels fordifferent CORESETS CORESET CORESET Number of EPDCCH candidates A B L = 2L = 4 L = 8 L = 16 L = 32 2 2 4, 4 2, 2 1, 1 0, 0 0, 0 4 4 3, 3 3, 3 1,1 1, 1 0, 0 8 8 3, 3 2, 2 1, 1 1, 1 1, 1 4 2 5, 3 3, 2 1, 1 1, 0 0, 0 82 4, 2 4, 2 1, 1 1, 0 1, 0 8 4 3, 3 2, 2 2, 1 1, 1 1, 0

Table 2 is merely an example of candidate numbers for respectiveaggregation levels for CORESTS of different sizes. It is to beunderstood that these are example values and are not intended to belimiting in nature.

In some implementations, in the time domain, a CORESET may comprise oneOFDM symbol or a set of contiguous or non-contiguous OFDM symbols. Theconfiguration for the CORESET may be defined in various different ways.For example, the CORESET can be defined based on a starting OFDM symboland a time duration. Another example may include defining a number ofOFDM symbols. In some embodiments, a CORESET may be configured with asingle Control Channel Element-to-Resource Element Group (CCE-to-REG)mapping.

FIGS. 3A and 3B illustrate example devices that may implement themethods and teachings according to this disclosure. In particular, FIG.3A illustrates an example ED 110, and FIG. 3B illustrates an examplebase station 170. These components could be used in the system 100 or inany other suitable system.

As shown in FIG. 3A, the ED 110 includes at least one processing unit200. The processing unit 200 implements various processing operations ofthe ED 110. For example, the processing unit 200 could perform signalcoding, data processing, power control, input/output processing, or anyother functionality enabling the ED 110 to operate in the system 100.The processing unit 200 may also be configured to implement some or allof the functionality and/or embodiments described in more detail above.Each processing unit 200 includes any suitable processing or computingdevice configured to perform one or more operations. Each processingunit 200 could, for example, include a microprocessor, microcontroller,digital signal processor, field programmable gate array, or applicationspecific integrated circuit.

The ED 110 also includes at least one transceiver 202. The transceiver202 is configured to modulate data or other content for transmission byat least one antenna or NIC (Network Interface Controller) 204. Thetransceiver 202 is also configured to demodulate data or other contentreceived by the at least one antenna 204. Each transceiver 202 includesany suitable structure for generating signals for wireless transmissionand/or processing signals received wirelessly or by wire. Each antenna204 includes any suitable structure for transmitting and/or receivingwireless signals. One or multiple transceivers 202 could be used in theED 110, and one or multiple antennas 204 could be used in the ED 110.Although shown as a single functional unit, a transceiver 202 could alsobe implemented using at least one transmitter and at least one separatereceiver.

The ED 110 further includes one or more input/output devices 206 orinterfaces. The input/output devices 206 facilitate interaction with auser or other devices (network communications) in the network. Eachinput/output device 206 includes any suitable structure for providinginformation to or receiving/providing information from a user, such as aspeaker, microphone, keypad, keyboard, display, or touch screen,including network interface communications.

In addition, the ED 110 includes at least one memory 208. The memory 208stores instructions and data used, generated, or collected by the ED110. For example, the memory 208 could store software instructions ormodules configured to implement some or all of the functionality and/orembodiments described above and that are executed by the processingunit(s) 200. Each memory 208 includes any suitable volatile and/ornon-volatile storage and retrieval device(s). Any suitable type ofmemory may be used, such as random access memory (RAM), read only memory(ROM), hard disk, optical disc, subscriber identity module (SIM) card,memory stick, secure digital (SD) memory card, and the like.

As shown in FIG. 3B, the base station 170 includes at least oneprocessing unit 250, at least one transmitter 252, at least one receiver254, one or more antennas 256, at least one memory 258, and one or moreinput/output devices or interfaces 266. A transceiver, not shown, may beused instead of the transmitter 252 and receiver 254. A scheduler 253may be coupled to the processing unit 250. The scheduler 253 may beincluded within or operated separately from the base station 170. Theprocessing unit 250 implements various processing operations of the basestation 170, such as signal coding, data processing, power control,input/output processing, or any other functionality. The processing unit250 can also be configured to implement some or all of the functionalityand/or embodiments described in more detail above. Each processing unit250 includes any suitable processing or computing device configured toperform one or more operations. Each processing unit 250 could, forexample, include a microprocessor, microcontroller, digital signalprocessor, field programmable gate array, or application specificintegrated circuit.

Each transmitter 252 includes any suitable structure for generatingsignals for wireless transmission to one or more EDs or other devices.Each receiver 254 includes any suitable structure for processing signalsreceived wirelessly or by wire from one or more EDs or other devices.Although shown as separate components, at least one transmitter 252 andat least one receiver 254 could be combined into a transceiver. Eachantenna 256 includes any suitable structure for transmitting and/orreceiving wireless signals. While a common antenna 256 is shown here asbeing coupled to both the transmitter 252 and the receiver 254, one ormore antennas 256 could be coupled to the transmitter(s) 252, and one ormore separate antennas 256 could be coupled to the receiver(s) 254. Eachmemory 258 includes any suitable volatile and/or non-volatile storageand retrieval device(s) such as those described above in connection tothe ED 110. The memory 258 stores instructions and data used, generated,or collected by the base station 170. For example, the memory 258 couldstore software instructions or modules configured to implement some orall of the functionality and/or embodiments described above and that areexecuted by the processing unit(s) 250.

Each input/output device 266 facilitates interaction with a user orother devices (network communications) in the network. Each input/outputdevice 266 includes any suitable structure for providing information toor receiving/providing information from a user, including networkinterface communications.

It should be appreciated that one or more steps of the embodimentmethods provided herein may be performed by corresponding units ormodules, according to FIGS. 3A and 3B. For example, a signal may betransmitted by a transmitting unit or a transmitting module. A signalmay be received by a receiving unit or a receiving module. A signal maybe processed by a processing unit or a processing module. The respectiveunits/modules may be hardware, software, or a combination thereof. Forinstance, one or more of the units/modules may be an integrated circuit,such as field programmable gate arrays (FPGAs) or application-specificintegrated circuits (ASICs). It will be appreciated that where themodules are software, they may be retrieved by a processor, in whole orpart as needed, individually or together for processing, in single ormultiple instances as required, and that the modules themselves mayinclude instructions for further deployment and instantiation.

A UE can monitor one or more control resource sets (CORESET) fordownlink control information. Long term Evolution (LTE) is known tosupport UE specific and/or case specific search space definitions. Atime/frequency resource set (i.e. control resource set) can be definedas a set of Resource Element Groups (REGs) under a given numerology. Insome implementations a REG is four consecutive Resource Elements (REs).An RE is a smallest transmission resource element, which may, forexample, be 1 symbol by 1 sub-carrier. A CORESET may be made up ofmultiples resource blocks (i.e, multiples of 12 REs) in the frequencydomain.

A search space for one search space type may be defined by at least someof the following properties: one or more aggregation levels (AL), anumber of decoding candidates (i.e. a candidate number (CN)) for eachaggregation level and a set of Control Channel Elements (CCEs) for eachdecoding candidate. A candidate is a location in the search space thatmay include downlink control information for the UE. Thus, a candidatenumber is a defined number of potential locations in the search space.In some implementations, a CCE may be nine consecutive REGs. Anaggregation level may be defined as 1, 2, 4, or 8 consecutive CCEs. Asan example, an aggregation level of 2 would be 2 consecutive CCEs.

In some implementations, in the time domain, a CORESET may comprise oneOFDM symbol or a set of contiguous or non-contiguous OFDM symbols. Theconfiguration for the CORESET may be defined in various different ways.For example, the CORESET can be defined based on a starting OFDM symboland a time duration. Another example may include defining a number ofOFDM symbols. In some embodiments, a CORESET may be configured with asingle Control Channel Element-to-Resource Element Group (CCE-to-REG)mapping.

FIG. 4A illustrates, for a single cell 6, an example of conventionalcommunication between a single TRP 2 and a single UE 4. FIG. 4A includesa representative example of a single Physical Downlink Control Channel(PDCCH) 8 being transmitted along with a single Physical Downlink SharedChannel (PDSCH) 9. One PDCCH 8 includes one assignment information forone PDSCH 9. One PDCCH 8 and/or one PDSCH 9 will be associated with acell radio network temporary identifier (C-RNTI) for identifying the UEthat the PDCCH and/or PDSCH is being transmitted for. It should be notedthat a same UE may have multiple C-RNTIs. In FIG. 4A, as PDCCH and/orPDSCH is for UE4, the C-RNTI identifies UE 4. The examples of the PDCCHand PDSCH in FIG. 4A are only intended to be representative. It is to beunderstood that an implementation specific scenario may include numerousUE, each having an allotted portion of the transmission resource forPDCCH and PDSCH.

Embodiments of the present disclosure pertain to communications betweenmultiple TRPs in a single cell and UEs. FIG. 4B illustrates, for aregion 16, an example of communication according to embodiments of thepresent application between a two TRPs, TRP 12 and TRP 13, and a singleUE 14. FIG. 4B includes an example of PDCCH1 18 a being transmittedalong with PDSCH1 19 a from TRP 12 and PDCCH2 18 b being transmittedalong with PDSCH2 19 b from TRP 13. PDCCH1 18 a is used to carry oneassignment for PDSCH1 19 a and PDCCH2 18 b is used to carry anotherassignment for PDSCH2 19 b. PDSCH 19 a and 19 b also are associated witha C-RNTI for identifying the UE that the assignment is for. In FIG. 4B,the C-RNTI identifies UE 14.

Embodiments of the present application include providing support fordifferent aspects of signaling between TRPs (or more generally from thenetwork side) and UEs when there are multiple PDCCH(s) for PDSCH and/orPUSCH, and a single data channel type (unicast or UE-specific), and oneRNTI type (C-RNTI or configurable UE ID) in a single cell. Someembodiments that will be described herein are i) providing support forsignaling the maximum number of PDCCH and an association between thePDCCH and other properties of a communication link, ii) providingsupport for detection of time unit information from multiple TRPs forthe single data channel type, iii) providing support for HARQ codebookand PUCCH resource, iv) providing support for PDCCH configurationspecific and control resource set specific, or both, search spacedefinition, v) providing support for maximum HARQ process number and anassociation between the PDCCH and the HARQ process number and vi)providing support for an association between the PDCCH and controlsignaling for UL channel (e.g. PUSCH and/or PUCCH) and/or referencesignal transmission (e.g. SRS).

In some implementations, there can be an association between PDCCH andother properties, such as the a control resource set, a QCLconfiguration, a radio network temporary identifier (RNTI) and/or aconfigurable UE ID, higher-layer sublayer, a HARQ entity, and a DMRSconfiguration.

Support for Assignment Association and Configuration

In some embodiments, a UE can be configured to monitor multiple PDCCHscarrying multiple assignments for multiple PDSCHs and/or multiple PUSCHsand each PDCCH is used to schedule a respective PDSCH or PUSCH, whereeach PDCCH and/or PDSCH is transmitted from a separate TRP which alsocan be transparent to UE. In this embodiment, multiple PDCCHs areassociated with single NR-cell and can be simultaneously monitored byone UE within the same one monitoring occasion which can be at least anOFDM symbol group, a slot, a mini slot, a slot group, and a sub-frame. Amini slot is a portion of a slot and thus less than a full slot. A slotgroup is a group of slots and thus more than a full slot. Moreover, insome implementations multiple PDCCHs for multiple PDSCHs or multiplePUSCHs are associated with a single data channel type (unicast orUE-specific) and one RNTI type with one or more C-RNTI and/or one ormore configurable UE ID (e.g. one C-RNTI1 is configured during randomaccess procedure and another C-RNTI2 or UE ID is configured using RRCsignaling). In a first example, a UE can be configured to monitor bothPDCCH1 and PDCCH2 for scheduling UE-specific PDSCH1 and PDSCH2,respectively. In a second example, the UE can be configured to monitorPDCCH1, PDCCH2, PDCCH3 and PDCCH4 for scheduling UE-specific PDSCH1,PDSCH2, PUSCH1 and PUSCH2, respectively. Generally, when referring toone or more PDCCH in the present application it is to be understood thatthis at least corresponds to at least one different PDCCH which can bemonitored simultaneously and associated with at least one UE-specificdata channel, for DL or UL, with a same RNTI type.

In some implementations, the number of one or more PDCCH can beexplicitly provided to the UE from the network, for example by broadcastsignaling.

In other implementations, the number of one or more PDCCH can beimplicitly derived from another property of the communication link. Thefollowing are a non-limiting list of examples of properties that thenumber could be implicitly derived from. A first example property is theCORESET group configuration that is associated with UE-specific searchspace for PDCCH monitoring. In this example, one or more CORESETsassociated with UE-specific search space will be split into one or moreCORESET groups and each CORESET group has at least one CORESET. Thenumber of one or more PDCCH is same as the number of one or moreconfigured CORESET groups. A second example property is aQuasi-Co-Location (QCL) association between a Demodulation ReferenceSignal (DMRS) of the PDCCH with one or more other DL Reference Signal(RS), for example a Channel Status Information—Reference Signal (CSI-RS)resource, and/or port information. In this example, the number of one ormore PDCCH is same as the number of one or more different associated QCLconfigurations. Moreover, one or more QCL configurations also can beassociated with at least one CORESET group that is associated with onesearch space type. A third example property is related to a high-layersublayer such as the Medium Access Control (MAC) layer, the Radio LinkControl (RLC) layer or the Packet Layer Convergence Protocol (PDCP)layer. In this example, the number of one or more PDCCH is same as thenumber of one or more MAC layer, or one or more RLC layer or one or morePDCP layer. A fourth example property is related to a HARQ entity. Inthis example, the number of one or more PDCCH is same as the number ofone or more HARQ entity. A fifth example property is related to aC-RNTI, or possibly a configurable UE-specific ID. In this example, thenumber of one or more PDCCH is same as the number of one or more C-RNTIand/or UE-specific ID which can be configured RAR (MAC CE) and/or RRCconfiguration. A sixth example property is DMRS configuration whichincludes at least one of port number and/or index, pattern and sequencegeneration initialization identifier (ID). In this example, the numberof one or more PDCCH is the same as the number of one or more DMRSconfiguration. Moreover, one or more DMRS configuration also can beassociated with at least one CORESET and/or at least one search spacewhich are associated with one search space type.

The network provides a UE with information detailing an associationbetween the PDCCH for UL or DL assignment associated with the samechannel type (unicast or UE-specific), one same RNTI type and anotherproperty. In a first example, each PDCCH is associated with specificCORESET group which is associated with specific CORESET group index. Inthis example, a first PDCCH is associated with a first CORESET group anda second PDCCH is associated with a second CORESET group. In a secondexample, each PDCCH is associated with specific QCL configurationbetween the DMRS of each PDCCH with other DL RS and specific QCLconfiguration is associated with a specific configuration index. In thisexample, a first PDCCH is associated with a first QCL configurationbetween the DMRS of a first PDCCH with other DL RS and a second PDCCH isassociated with a second QCL configuration between the DMRS of thesecond PDCCH with other DL RS. Moreover, multiple QCL configurationsalso can be associated with at least one CORESET group and one searchspace type. In a third example, each PDCCH is associated with a specifichigh-layer sublayer such as the Medium Access Control (MAC) layer, theRadio Link Control (RLC) layer or the Packet Layer Convergence Protocol(PDCP) layer and each high-layer sublayer is associated with a specifichigh-layer sublayer index. In this example, a first PDCCH is associatedwith a first high-layer sublayer and a second PDCCH is associated with asecond high-layer sublayer. In a fourth example, each PDCCH isassociated with specific HARQ entity with specific HARQ entity index. Inthis example, a first PDCCH is associated with a first HARQ entity and asecond PDCCH is associated with a second HARQ entity. A fifth example,each PDCCH is associated with specific C-RNTI and/or UE specific IDwhich is associated with a specific index, In this example, a firstPDCCH is associated with a first C-RNTI and a second PDCCH is associatedwith a second C-RNTI, or possibly a configurable UE-specific ID. In asixth example, each PDCCH is associated with a specific DMRSconfiguration for PDCCH and DMRS configuration is associated with aspecific DMRS configuration index. In this example, a first PDCCH isassociated with a first DMRS configuration and a second PDCCH isassociated with a second DMRS configuration. Moreover, multiple DMRSconfigurations also can be associated with at least one CORESET groupand/or at least one search space and one search space type. Generally,first and/or second can be regarded as the identity for PDCCH/assignmentwhich can be associated with at least one of CORESET group index, QCLconfiguration index, high-layer sublayer index, HARQ entity index,C-RNTI/configurable ID index, and DMRS configuration index.

FIG. 5 includes a table having two rows and seven columns. The first rowidentifies six possible properties that could be associated with a firstPDCCH (PDCCH1) that a UE may be monitoring and the second row identifiessix similar properties that could be associated with a second PDCCH(PDCCH2) that the UE may be monitoring. The six properties are the sameas those identified above, CORESET group, QCL association between DMRSof PDCCH with CSI-RS, higher layer sublayer, HARQ entity, UE identifierand DMRS configuration of PDCCH. A PDCCH could be associated with anyone or a combination of more than one of the properties identified inthe table. The association with one or more of the properties can beupdated by the network if and when desired. While only two PDCCH andpossible associated properties are indicated in FIG. 5 , it isunderstood that appropriate associations for each PDCCH that the UE ismonitoring would be provided to the UE by the network.

In some implementations, the UE may monitor only PDCCHs that have anassociated CORESET group or a QCL association between DMRS of PDCCH withCSI-RS, or both.

In some implementations, one PDCCH can be monitored that is identifiedin the association that is one specific CORESET group, which is a subsetof all CORESET defined for one search space type. This would beconsidered a UE-specific search space.

In some implementations, the UE may monitor multiple PDCCHs that areassociated to only one CORESET group and each PDCCH is associated with aQCL configuration between the DMRS of the PDCCH with other DL RS.

PDCCH Identity Specific Search Space Splitting

In some embodiments, a UE can be configured by the network to monitor atleast two different CORESET groups that are for a particular UE-specificsearch space. In such embodiments, different PDCCH can be associatedwith different CORESET groups and each CORESET group has at least oneCORESET. Moreover, each CORESET group can have specific search spacedefinition including specific aggregation level and/or candidate number.

Some aspects of the present disclosure also pertain to defining theconfiguration of the transmission mode for a single or multiple PDCCH.In this disclosure, one specific transmission mode may be associatedwith one specific DCI format. Generally, different DCI formats providedifferent scheduling information and can have the same or a differentpayload size, which refers to one total bit number of one DCI. (Solution1-1) In some embodiments with multiple PDSCH/PUSCH transmission withsimilar spatial channel character, one common transmission modeconfiguration can achieve performance gain without extra configurationoverhead. In some embodiments with multiple PDSCH/PUSCH transmissionwith different spatial channel character, specific transmission modeconfiguration supporting flexible transmission schemes matching thespecific channel may achieve increased performance gain without limitingconfiguration overhead.

Aspects of the present disclosure relate to providing a common PDCCHconfiguration, for the case of monitoring either single or multiplePDCCH. Some implementations of the common configuration can be based onan explicit mechanism of the network informing the UE the parameters ofthe configuration. Some implementations of the common configuration canbe based on an implicit mechanism of the UE determining relevantinformation about the configuration based on one or more associationswith information known to the UE.

In some embodiments, the common configuration utilizes M PDCCHidentifiers (M≥2) for each CORESET configuration, wherein each PDCCHidentifier indicates two candidate values (e.g. 0/1, on/off, ortrue/false, etc.) to identify one PDCCH to be monitored in therespective CORESET (Solution 1-2-0). In some embodiments, the commonconfiguration utilizes a single PDCCH identifier for each CORESETconfiguration, wherein each PDCCH identifier indicates M candidatevalues (e.g. 1,2, . . . M) to identify one of maximum M PDCCH (M≥2) tobe monitored in the respective CORESET (Solution 1-2-1). For both ofthese aspects of the disclosure, there can be a single or M individualPDCCH identifiers, or there can be a single or M pairs of PDCCHidentifiers where each pair includes an downlink PDCCH identifier and anuplink PDCCH identifier. For embodiments mentioned in this section, thenumber of PDCCH and association between PDCCH and CORESET are determinedby the CORESET configuration. In some embodiments with multiple PDCCHtransmission with ideal scheduling coordination, a flexible associationbetween PDCCH and CORESET with multiple identifiers supporting flexibleresource allocations for PDCCH may achieve increased performance gainwithout limiting configuration overhead. In other embodiments withmultiple PDCCH transmission with non-ideal scheduling coordinationwherein flexible resource allocation for PDCCH is hard to realize, alimited association between PDCCH and CORESET with a single identifiercan achieve performance gain without limiting configuration overhead

With regard to an explicit mechanism with a separate indication of PDCCHnumber, in some embodiments, a predefined association is used betweenPDCCH and CORESET, for example a mapping between PDCCH and CORESET. Insome implementations, the association, for example, could be in the formof a table or rule (can be regarded as Solutions 1-3-0). In some otherimplementations, the association can be also determined by the CORESETconfiguration. (Solutions 1-3-1 and 1-3-2). For embodiments mentioned inthis section, the number of PDCCH is at least explicitly indicated inaddition to CORESET configuration. In some embodiments, for some UE witha limited ability to support multiple PDCCH detection, it may not benecessary to support flexible maximum PDCCH number configuration. Thenthe PDCCH number can be separately configuration with limitedflexibility. Moreover, for some UE with limited capability to supportingblind decoding for PDCCH monitoring, a limited association between PDCCHand CORESET can be supported. Then a predefined association can be abetter solution without any extra configuration overhead. In someembodiments with multiple PDCCH transmission and with ideal schedulingcoordination, a flexible association between PDCCH and CORESET withmultiple identifiers supporting flexible resource allocation for PDCCHcan achieve increased performance gain without limit configurationoverhead. In some embodiments with multiple PDCCH transmission withnon-ideal scheduling coordination wherein flexible resource allocationfor PDCCH is hard to realize, a limited association between PDCCH andCORESET with a single identifier can achieve performance gain withoutlimiting configuration overhead.

Some aspects of the present disclosure pertain to a monitoringconfiguration for PDCCH that is not common to all association casesbetween PDCCH and CORESET. In some embodiments, an explicitconfiguration is used to indicate to the UE to use a differentassociation between PDCCH and CORESET. For example, with thisconfiguration, different PDCCH can be monitored from different CORESET,otherwise, different PDCCH can be monitored from one same CORESET.(Solution 1-4). In some embodiments, for UEs with a different capabilityof supporting blind decoding for PDCCH monitoring, different UEs can beconfigured with specific association between PDCCH and CORESET. Based ona separate association configuration between PDCCH and CORESET fordifferent cases, CORESET configuration does not necessarily need extrainformation related to association between PDCCH and CORESET.

Some aspects of the present disclosure pertain to utilizing PDCCHspecific scrambling to realize interference randomization. In someembodiments, PDCCH identity or index can be used to scramble associatedPDCCH/PDCHS/PUSCH channels. (Solution 2-1) In some embodiments, multiplechannels simultaneously transmitted from or received by one UE canachieve further interference randomization based on the specificscrambling initial value for the performance gain.

Some aspects of the present disclosure pertain to PUCCH resourceconfiguration for any of PUCCH with common configuration, PUCCH forseparate configuration or a hybrid of both common and separateconfiguration. In some embodiments, at least one PUCCH resource can beassociated with at least one PDCCH/PDSCH that is to be monitored withinone time interval, such as a slot. (Solutions 3-1 and 3-2) In someembodiments, there is also provided a manner for reporting the PUCCHfeedback mode. (Solution 3-3) In some embodiments with multiple PDSCHtransmissions with ideal coordination, one PUCCH solution can make fulluse of the best channel out of multiple channels associated withmultiple PDSCH transmissions without any feedback delay. In someembodiments with multiple PDSCH transmissions with non-idealcoordination, one PUCCH may face an unacceptable feedback delay.Separate PUCCH can make full use of a specific best channel for feedbackwithout any feedback delay.

Some aspects of the present disclosure pertain to PUSCH associatedCSI-RS measurement feedback in which the different CSI-RS measurementand feedback occurs in separate PUSCH. (Solution 4-1) In someembodiments, a specific association between different PUSCH anddifferent CSI-RS measurements and reports can achieve lower delay.

Solution 1-1

Some embodiments of the present disclosure are related to determining aconfiguration to be used for transmission of multiple PDCCH from a TRPto a UE and for PDCCH monitoring by a UE. An example method includes theTRP determining a transmission mode for at least one PDCCH for PDSCHand/or PUSCH. The determination may be made based on at least one of asingle transmission mode configuration that is common for one or morePDCCH or a specific transmission mode configuration for each PDCCH.

In the embodiment of the single transmission mode configuration, thesingle transmission mode configuration that is common for one or morePDCCH for PDSCH and/or PUSCH can be predefined. In this embodiment, asingle transmission mode configuration will be indicated to the UEthrough one signaling (e.g. RRC). Then UE will assume multiple PDCCHhave the same transmission mode configuration from the signaling. FIG.6A illustrates a representation of a single common transmission modeconfiguration 510 that is applied for transmitting/monitoring a singlePDCCH or multiple PDCCH 515.

In the embodiment of the specific transmission mode (TM) configuration,the specific transmission mode configuration for each PDCCH for PDSCH orPUSCH can be signaled to the UE using a signaling (e.g., RRC signaling),Downlink Control Information (DCI), Media Access Control Control Element(MAC CE). Then UE will assume each PDCCH has one specific transmissionmode configuration from the signaling. In some implementations, thespecific transmission mode configuration also implies a PDCCH number forPDSCH or PUSCH, or both, within one monitoring occasion (e.g. slot)based on a transmission mode configuration number. In a first example,the UE may be configured for PDSCH with TM1 and TM2, then the number ofPDCCH for PDSCH can be determined as 2. In a second example, the UE maybe configured for PUSCH with TM3 and TM4, then the number of PDCCH forPUSCH can be determined as 2. It may be that TM1 and TM2 are equivalentto TM3 and TM4, respectively, in the first and second examples, but thatis not always the case.

FIG. 6B illustrates a representation of two separate transmission modeconfigurations that are applied for transmitting/monitoring a respectivePDCCH, i.e. TM configuration 1 520 used for PDCCH1 525 and TMconfiguration 2 530 used for PDCCH2 535.

FIG. 17 is a flow chart describing a method according to an aspect ofthe present application. Step 1710 involves receiving a signalingincluding a transmission mode configuration for two or more PhysicalDownlink Control Channels (PDCCHs). Step 1720 involves determining atransmission mode for the two or more Physical Downlink Control Channels(PDCCHs) based on the transmission mode configuration.

In some embodiments, the transmission mode configuration is common fortwo or more PDCCHs.

In some embodiments, the transmission mode is predefined.

In some embodiments, the transmission mode configuration indicates arespective transmission mode for each of the two or more PDCCHs.

In some embodiments, the transmission mode is different for each of theat least one PDCCH for PDSCH or PUSCH.

In some embodiments, the received transmission mode configuration issignaled using at least one of Radio Resource Control (RRC) signaling,Downlink Control Information (DCI), Media Access Control Control Element(MAC CE).

In some embodiments, a device that performs methods described above isan electronic device, such as a UE or baseband chip. A general exampleof such a device is described in FIG. 3A.

With regard to the implementation details of the transmission modeconfiguration, reference can be made to the above-discussed embodiments,with their combination and modification falling within the scope of thepresent application.

Solution 1-2-0

Some embodiments of the present disclosure are related to a UEmonitoring one or more PDCCH for PDSCH and/or PUSCH within a monitoringoccasion (e.g. slot). It is to be understood that the monitoringoccasion could be a subslot (less than a slot) or multiple slots, orsome other time duration. The slot can be a time duration definition.Moreover, based on CORESET configuration, the UE determines the numberof PDCCH and an association between PDCCH and CORESET that should beclear for monitoring PDCCH for PDSCH and/or PUSCH.

In some implementations, the UE monitors an integer value P of PDCCH,where P is greater than or equal to one, within a monitoring occasion.The PDCCH that are being monitored can be configured for PDSCH or PUSCH,or both, within at least one CORESET. The at least one CORESET can beassociated with one search space type (e.g. UE specific). Each CORESETconfiguration may include M PDCCH identifiers (PDCCHIdx), where M≥2 suchthat the M PDCCH identifiers may be defined as PDCCHIdxm, m={1 . . . M}.In these implementations, each PDCCH identifier is used to indicate if arespective PDCCH (PDCCH with index m) should be monitored in aparticular CORESET wherein each PDCCH identifier can indicate twocandidate values (e.g. 0/1, on/off, or true/false, etc). If M=2, amaximum of 2 PDCCHs can be configured to be monitored in a particularCORESET. More generally, M can be greater than 2. Then, based on oneexact value of a PDCCH identifier, i.e. PDCCHIdxm, PDCCH with index m, aparticular one of the two PDCCH can be indicated to be monitored or notmonitored. Moreover, this CORESET configuration including 2 PDCCHidentifiers can be signaled to the UE with a signaling, e.g. a RRCsignaling, then the UE monitors one PDCCH from the specific CORESETaccording to the associated identifier value. The CORESET configurationwith M PDCCH identifiers can also imply that the exact number P of PDCCHfor monitoring is not larger than M. One COREST can be configured tomonitor one or more PDCCHs.

Based on an association between the CORESET and the PDCCH identifiers,the UE can monitor the mth PDCCH from all CORESET for which the PDCCHidentifier PDCCHIdxm indicates that the mth PDCCH should be monitored.In a particular example, if PDCCHIdxm=1, then the UE should monitor themth PDCCH and if PDCCHIdxm=0, the UE should not monitor the mth PDCCH.The value P is equal to the total number of all indexes m for whichPDCCHIdxm=1 from all CORESET, i.e. PDCCH that are to be monitored. In afirst example, for two CORESET with M=2 PDCCH identifiers, PDCCHIdx1 andPDCCHIdx2, a value of two PDCCH identifiers from two CORESETconfigurations are explained as {(PDCCHIdx1=1, PDCCHIdx2=0),(PDCCHIdx1=1, PDCCHIdx2=0)} indicates only PDCCH1 is to be monitored inboth CORESET, meanwhile P=1. In a second example, for two CORESET aconfiguration of PDCCH identifiers {(PDCCHIdx1=1, PDCCHIdx2=1),(PDCCHIdx1=1, PDCCHIdx2=0)} indicates PDCCH1 is to be monitored in bothCORESET and PDCCH2 is to be monitored in only the first CORESET,meanwhile P=2. In a third example, for two CORESET a configuration ofPDCCH identifiers {(PDCCHIdx1=1, PDCCHIdx2=0), (PDCCHIdx1=0,PDCCHIdx2=1)} indicates PDCCH1 is to be monitored in only the firstCORESET and PDCCH2 is to be monitored in only second CORESET meanwhileP=2;

If the UE is configured to monitor the PDCCH for PDSCH, then the UEmonitors P PDCCH for PDSCH. If the UE is configured to monitor the PDCCHfor PUSCH, then the UE monitors P PDCCH for PUSCH.

In some implementations, the PDCCH configuration for PDSCH and PUSCH isa common configuration for both PDSCH and PUSCH.

In some embodiments, each PDCCH can be associated with one, more thanone, or all of the CORESET. Downlink and uplink components of the PDCCHcan share the same CORESET configuration.

FIGS. 7A to 7E illustrate multiple examples of the relationship betweenone or more CORESET, one or more PDCCH, and one or more PDCCHidentifiers, where M is equal to 2, i.e. there are a maximum of twoPDCCHs that can be monitored in a given CORESET. Therefore, there aretwo PDCCH identifiers, PDCCHIdx1 associated with a first PDCCH (PDCCH1)and PDCCHIdx2 associated with a second PDCCH (PDCCH2).

FIG. 7A illustrates an example of a single CORESET (CORESET0) having asingle PDCCH (PDCCH1) that is to be monitored. A second PDCCH2 does notneed to be monitored in CORESET0. Since only PDCCH1 needs to bemonitored, PDCCHIdx1=1 (monitor) and PDCCHIdx2=0 (do not monitor).

FIG. 7B illustrates an example of a single CORESET (CORESET0) having twoPDCCH (PDCCH1 and PDCCH2) that are to be monitored. Since both PDCCH1and PDCCH2 need to be monitored, PDCCHIdx1=1 (monitor) and PDCCHIdx2=1(monitor).

FIG. 7C illustrates an example of two CORESET (CORESET0 and CORESET1)for which only one PDCCH (PDCCH1) is to be monitored. For CORESET0,PDCCH1 needs to be monitored so PDCCHIdx1=1 (monitor) and PDCCH2 doesnot need to be monitored so PDCCHIdx2=0 (do not monitor). For CORESET1,again PDCCH1 needs to be monitored so PDCCHIdx1=1 (monitor) and PDCCH2does not need to be monitored so PDCCHIdx2=0 (do not monitor).

FIG. 7D illustrates an example of two CORESET (CORESET0 and CORESET1)each having a respective PDCCH (PDCCH1 for CORESET0 and PDCCH2 forCORESET1) that is to be monitored. For CORESET0, PDCCH1 needs to bemonitored so PDCCHIdx1=1 (monitor) and PDCCH2 does not need to bemonitored so PDCCHIdx2=0 (do not monitor). For CORESET1, PDCCH1 does notneed to be monitored so PDCCHIdx1=0 (do not monitor) and PDCCH2 needs tobe monitored so PDCCHIdx2=1 (monitor).

FIG. 7E illustrates an example of two CORESET (CORESET0 and CORESET1) inwhich CORESET0 has PDCCH1 to be monitored and CORESET1 has both PDCCH1and PDCCH2 that are to be monitored. For CORESET0, PDCCH1 needs to bemonitored so PDCCHIdx1=1 (monitor) and PDCCH2 does not need to bemonitored so PDCCHIdx2=0 (do not monitor). For CORESET1, since bothPDCCH1 and PDCCH2 need to be monitored, PDCCHIdx1=1 (monitor) andPDCCHIdx2=1 (monitor).

FIGS. 8A to 8E illustrates multiple examples of the relationship betweenone or more CORESET, one or more PDCCH, and one or more PDCCHidentifiers, for a maximum of M PDCCHs that can be monitored in a givenCORESET. The examples in FIGS. 8A to 8E generally correspond to theexamples shown in FIGS. 7A to 7E, except there are M PDCCH identifiersthat are set to either 0 or 1, depending if the PDCCH is to be monitoredor not.

The examples shown in FIGS. 7A to 7E and 8A to 8E are non-exhaustiveexamples and one skilled in the art would understand how furtherpermutations could be defined based on the provided examples.

FIG. 9 is an example of a flow chart 980 in which steps are performed bymultiple components of a network. In step 982, a network side devicetransmits at least one CORESET configuration and each CORESETconfiguration includes multiple PDCCH identifiers with specific values.The at least one CORESET configuration may be transmitted in asignaling, e.g., RRC signaling. In step 984, a UE receives the at leastone CORESET configuration. In step 986, the UE checks values of multiplePDCCH identifiers included in the at least one CORESET configurationthat identifies at least one PDCCH to be monitored. In step 988, the UEmonitors the at least one identified PDCCH in at least one CORESETcorresponding to the least one CORESET configuration. The implementationdetails of the CORESET configuration may be referred to the embodimentsas discussed above.

In some embodiments, a device that performs a method described above isan electronic device, such as a UE, or a network device, such as a basestation. A general example of such a device is described in FIG. 3A andFIG. 3B.

Other embodiments include the UE monitoring P_(DL) PDCCH and P_(UL)PDCCH within the monitoring occasion for PDSCH/PUSCH from at least oneCORESET, wherein each CORESET configuration may include two sets of MPDCCH identifiers (PDCCHIdx), where M≥1 such that the PDCCHDLIdxm, m=1,. . . ,M and PDCCHULIdxm, m=1, . . . ,M. In such an implementation, thedownlink and uplink components of the PDCCH have separate CORESETconfigurations based on a specific set of M PDCCH identifiers. TheCORESET is associated with one search space type.

In some implementations, the UE can monitor the mth PDCCH for PDSCH fromall CORESET for which the PDCCH identifier PDCCHIdxm indicates that themth PDCCH, should be monitored. For example, if PDCCHDLIdxm=1, then theUE should monitor the mth PDCCH for PDSCH and if PDCCHDLIdxm=0, the UEshould not monitor the mth PDCCH. If PDCCHULIdxm=1, then the UE shouldmonitor the mth PDCCH for PUSCH and if PDCCHULIdxm=0, the UE should notmonitor the mth PDCCH. P_(DL) equals of all indexes m for PDCCHDLIdxm=1for PDSCH and P_(UL) equals the total number of all indexes m forPDCCHULIdxm=1 for PUSCH from all CORESET.

If configured to monitor PDCCH for PDSCH, the UE monitor P_(DL) PDCCHfor PDSCH. If configured to monitor PDCCH for PUSCH, the UE monitorsP_(UL) PDCCH for PUSCH.

In some embodiments, the PDCCH configuration for PDSCH and PUSCH areseparate configurations for both PDSCH and PUSCH.

FIGS. 10A to 10C illustrate multiple examples of the relationshipbetween one or more CORESET, one or more PDCCH, and one or more PDCCHidentifiers, where M is equal to 2, i.e. there are a maximum of twoPDCCHs that can be monitored for UL and a maximum of two PDCCHs that canbe monitored for DL within a particular CORESET. Therefore, there arefour PDCCH identifiers, PDCCHDLIdx1 and PDCCHULIdx1 associated with afirst PDCCH (PDCCH1_DL or PDCCH1_UL) and PDCCHDLIdx2 and PDCCHULIdx2associated with a second PDCCH (PDCCH2_DL or PDCCH2_UL).

FIG. 10A illustrates an example of a single CORESET (CORESET0) having afirst PDCCH1 with DL information (PDCCH1_DL) and UL information(PDCCH1_UL) to be monitored. A second PDCCH2 with DL information(PDCCH2_DL) and UL information (PDCCH2_UL) are not to be monitored.Since there are PDCCH1_UL and PDCCH1_DL to be monitored,PDCCHDLIdx1=1(monitor) and PDCCHULIdx1=1 (monitor). As there is nosecond PDCCH2 (i.e. PDCCH2_DL and PDCCH2_UL) to monitor, thenPDCCHDLIdx2=0 (do not monitor) and PDCCHULIdx2=0 (do not monitor).

FIG. 10B illustrates an example of a single CORESET (CORESET0) having afirst PDCCH1 with DL information (PDCCH1_DL) and UL information(PDCCH1_UL) to be monitored and a second PDCCH2 with DL information(PDCCH2_DL) to be monitored. Since there are PDCCH1_UL, PDCCH1_DL andPDCCH2_DL that need to be monitored, PDCCHDLIdx1=1 (monitor)PDCCHULIdx1=1 (monitor), and PDCCHDLIdx2=1 (monitor). As there is noPDCCH1_UL to be monitored, PDCCHULIdx2=0 (do not monitor). FIG. 8Cillustrates an example of two CORESET (CORESET0 and CORESET1). ForCORESET0, a first PDCCH1 with DL information (PDCCH1_DL) and ULinformation (PDCCH1_UL) are to be monitored and a second PDCCH2 with ULinformation (PDCCH2_UL) is to be monitored. Since there are PDCCH1_UL,PDCCH1_DL and PDCCH2_UL that need to be monitored, PDCCHDLIdx1=1(monitor), PDCCHULIdx1=1 (monitor), and PDCCHULIdx2=1 (monitor). Asthere is no PDCCH2_DL to be monitored, PDCCHDLIdx2=0 (do not monitor).For CORESET1, a first PDCCH1 with UL information (PDCCH1_UL) is to bemonitored and a second PDCCH2 with DL information (PDCCH2_DL) and ULinformation (PDCCH2_UL) are to be monitored. Since there are PDCCH1_UL,PDCCH2_DL and PDCCH2_UL that need to be monitored,PDCCHULIdx1=1(monitor) PDCCHDLIdx2=1(monitor), and PDCCHULIdx2=1(monitor). As there is no PDCCH1_DL to be monitored, PDCCHDLIdx1=0 (donot monitor).

FIGS. 11A to 11D illustrates multiple examples of the relationshipbetween one or more CORESET, one or more PDCCH, and one or more PDCCHidentifiers, for a maximum of M PDCCHs that can be monitored in a givenCORESET. The first three of the examples in FIGS. 11A to 11C generallycorrespond to the examples shown in FIGS. 10A to 10C, except there are MPDCCH identifiers for each of UL and DL that are set to either 0 or 1,depending if the PDCCH is to be monitored or not. FIG. 11D illustrates ascenario in which there are M CORESET and up to M PDCCH that could bemonitored for UL or DL, or both.

The examples shown in FIGS. 10A to 10C and 11A to 11D are non-exhaustiveexamples and one skilled in the art would understand how furtherpermutations could be defined based on the provided examples.

Solution 1-2-1

Other embodiments include the UE monitoring P PDCCH within a monitoringoccasion (e.g. slot) for PDSCH and/or PUSCH from at least one CORESET.In some implementations, each CORESET configuration includes a singlePDCCH identifier, i.e. PDCCHIdx, wherein each PDCCH identifier canindicate M candidate values (e.g. 1, 2, . . . M, M≥1). There can be amaximum M PDCCH that could be monitored from all CORESET, but in someinstances only a single PDCCH may be monitored per CORESET. One exactvalue of a single PDCCH identifier, m is used to indicate if a PDCCHwith index m should be monitored in a particular CORESET. Actually, thenumber of PDCCH to monitor, P is determined by the total number of PDCCHidentifiers with different values from all configured CORESET. Moreover,this configuration can be signaled with RRC. The RRC can also imply thatthe exact number P of PDCCH for monitoring is not larger than M.

The PDCCH identifier PDCCHIdx=m is used to indicate the PDCCH with indexm (1≤m≤M) should be monitored in a given CORESET. In a first example,for two CORESET with M=2 PDCCH identifiers, a configuration of PDCCHidentifiers defined as {PDCCHIdx=1, PDCCHIdx=1)} indicates only PDCCH1needs to be monitored from both two CORESET meanwhile P=1. In a secondexample, for two CORESET with M=2 PDCCH identifiers, a configuration ofPDCCH identifiers defined as {PDCCHIdx=1, PDCCHIdx=2)} indicates PDCCH1is to be monitored from only the first CORESET and PDCCH2 is to bemonitored from only the second CORESET, meanwhile P=2. In a thirdexample, for two CORESET with M=2 PDCCH identifiers, a configuration ofPDCCH identifiers defined as {PDCCHIdx=2, PDCCHIdx=2)} indicates onlyPDCCH2 needs to be monitored from both CORESET, meanwhile P=1. It can beunderstood that the configuration for this third example is the same asthe first example, because the UE may regard P PDCCH with a continuousindex starting from 1 to P (P≤M).

In some embodiments, when the UE is configured to monitor PDCCH forPDSCH, the UE monitors P PDCCH for PDSCH. In some embodiments, when theUE is configured to monitor PDCCH for PUSCH, the UE monitors P PDCCH forPUSCH.

In some implementations, the PDCCH configuration for PDSCH and PUSCH area common configuration for both PDSCH and PUSCH.

FIGS. 12A to 12C illustrate multiple examples of the relationshipbetween one or more CORESET, one or more PDCCH, and one or more PDCCHidentifiers, where M is equal to 2, i.e. there are a maximum of twoPDCCHs that can be monitored, but only one per CORESET. Therefore, thereis a single PDCCH identifier, PDCCHIdx associated with each of two PDCCH(PDCCH1 andPDCCH2).

FIG. 12A illustrates an example of a single CORESET (CORESET0) having afirst PDCCH (PDCCH1) to be monitored. Since there is only PDCCH1 thatneeds to be monitored, PDCCHIdx=1(monitor PDCCH1).

FIG. 12B illustrates an example of two CORESET (CORESET0 and CORESET1).For both CORESET0 and CORESET1, PDCCH1 is to be monitored. Therefore,for both CORESET0 and CORESET1, PDCCHIdx=1 (monitor PDCCH1).

FIG. 12C illustrates an example of two CORESET (CORESET0 and CORESET1).For CORESET0, PDCCH1 is to be monitored and for CORESET1, PDCCH2 is tobe monitored. Therefore, for CORESET0, PDCCHIdx=1(monitor PDCCH1) andfor CORESET1, PDCCHIdx=2 (monitor PDCCH2).

The three examples shown in FIGS. 12A to 12C are non-exhaustive examplesand one skilled in the art would understand how further permutationscould be defined based on the particular examples.

FIG. 12D is an example of a flow chart 1280 in which steps are performedby multiple components of the network. The example of FIG. 12D is for ascenario of M=2, i.e. there are only two PDCCH that could be monitored.In step 1282, a network side device transmits at least one CORESETconfiguration and each CORESET configuration includes a single PDCCHidentifier with specific values. In step 1284, a UE receives the atleast one CORESET configuration. In step 1286, the UE checks a value ofthe PDCCH identifier included in the at least one CORESET configurationthat identifies at least one PDCCH to be monitored. In step 1288, the UEmonitors the at least one PDCCH in at least one CORESET corresponding toat least one CORESET configuration. In step 1288, the UE monitors PDCCH1from all CORESET with a PDCCHIdx=1 or PDCCH2 from all CORESET with aPDCCHIdx=2, or both. More generally, if there were more PDCCH that couldbe monitored, then there would be a larger number of PDCDH identifiers.The implementation details of the CORESET configuration may be referredto the embodiments as discussed above.

In some embodiments, a device that performs a method described above isan electronic device, such as a UE, or a network device, such as a basestation. A general example of such a device is described in FIG. 3A andFIG. 3B.

In another implementation, each CORESET configuration includes two PDCCHidentifiers one for downlink and one for uplink, i.e. PDCCHDLIdx andPDCCHULIdx wherein different PDCCH identifiers may indicate the same ora different candidate value. For example, the same candidate value canbe (1,2, . . . M), M≥1 while a different candidate value can be (1,2, .. . M1, M1≤1) and (1,2, . . . M2, M2≤1) for DL and UL respectively. In acase where M=2, a first PDCCH, PDCCH1, has an associated PDCCH DLidentifier PDCCHDLIdx=1 and an associated PDCCH UL identifierPDCCHULIdx=1. A second PDCCH, PDCCH2, has an associated PDCCH DLidentifier PDCCHDLIdx=2 and an associated PDCCH UL identifierPDCCHULIdx=2. The PDCCH DL and UL identifiers can each be equal toeither 1 or 2.

In a particular example for M=2, the UE monitors PDCCH1 from all CORESETwith an identifier PDCCHDLIdx=1 for PDSCH and/or PDCCH2 from all CORESETwith an identifier PDCCHDLIdx=2 for PDSCH. The UE monitors PDCCH1 fromall CORESET with an identifier PDCCHULIdx=1 for PUSCH and/or PDCCH2 fromall CORESET with an identifier PDCCHULIdx=2 for PUSCH.

The value of P is equal to the total number of all of the differentPDCCHDLIdx (i.e. P_DL) or PDCCHULIdx (i.e. P_UL) for a given group ofCORESET. For example, P_DL is equal to 1 for a group of CORESET withonly PDCCHDLIdx=1 or PDCCHDLIdx=2. P_DL is equal to 2 for a group ofCORESET that have at least one CORESET with PDCCHDLIdx=1 and at leastone CORESET with PDCCHDLIdx=2.

In some embodiments, when the UE is configured to monitor PDCCH forPDSCH, the UE monitors P PDCCH for PDSCH. In some embodiments, when theUE is configured to monitor PDCCH for PUSCH, the UE monitors P PDCCH forPUSCH

In some implementations, the PDCCH configuration for PDSCH and PUSCH areseparate configurations for both PDSCH and PUSCH.

FIGS. 13A and 13B illustrate multiple examples of the relationshipbetween one or more CORESET, one or more PDCCH, and one or more PDCCHidentifiers, where M is equal to 2, i.e. there are a maximum of twoPDCCHs that can be monitored, for UL and DL. Therefore, there are twoPDCCH identifiers, PDCCHDLIdx associated with either a first PDCCH(PDCCH1_DL) or a second PDCCH (PDCCH2_DL) for PDSCH and PDCCHULIdxassociated with the first PDCCH (PDCCH1_UL) or the second PDCCH(PDCCH2_UL) for PUSCH.

FIG. 13A illustrates an example of a single CORESET (CORESET0) having afirst PDCCH1 with DL information (PDCCH1_DL) and UL information(PDCCH1_UL) to be monitored. Since there are PDCCH1_UL and PDCCH1_DLthat need to be monitored, PDCCHDLIdx=1(monitor PDCCH1_DL) andPDCCHULIdx=1 (monitor PDCCH1_UL).

FIG. 13B illustrates an example of two CORESET (CORESET0 and CORESET1).For CORESET0, a first PDCCH1 with DL information (PDCCH1_DL) and ULinformation (PDCCH1_UL) are to be monitored. Since there are PDCCH1_ULand PDCCH1_DL that need to be monitored, PDCCHDLIdx=1(monitor PDCCH1_DL)and PDCCHULIdx=1(monitor PDCCH1_UL). For CORESET1, a first PDCCH1 withUL information (PDCCH1_UL) is to be monitored and a second PDCCH2 withDL information (PDCCH2_DL) is to be monitored. Since there are PDCCH1_ULand PDCCH2_DL that need to be monitored, PDCCHULIdx=1(monitor PDCCH1_UL)and PDCCHDLIdx=2 (monitor PDCCH2_DL).

The two examples shown in FIGS. 13A and 13B are non-exhaustive examplesand one skilled in the art would understand how further permutationscould be defined based on the particular examples.

FIG. 18 is a flow chart describing a method according to an aspect ofthe present application. Step 1810 involves receiving at least oneControl Resource Set (CORESET) configuration. Step 1820 involvesmonitoring one or more Physical Downlink Control Channels (PDCCH) in atleast one CORESET within a monitoring occasion based on the at least oneCORESET configuration. Each CORESET configuration has at least one PDCCHidentifier used to indicate a number of PDCCH and an association betweena PDCCH and a CORESET.

In some embodiments, one PDCCH identifier includes one PDCCH identifierwhich is common for PDSCH and PUSCH.

In some embodiments, one PDCCH identifier includes one PDCCH identifierset including one specific PDCCH identifier for PDSCH and one specificPDCCH identifier for PUSCH.

In some embodiments, at least one PDCCH identifier of each CORESETconfiguration refers to M PDCCH identifiers, where M is an integer ≥1,and each of the M PDCCH identifiers is used to indicate whether aparticular PDCCH of the maximum M PDDCH is monitored or is not monitoredin the CORESET.

In some embodiments, each of the M PDCCH is associated with one specificPDCCH identifier of the M PDCCH identifiers.

In some embodiments, each of the M PDCCH is indicated to be monitored,or not, based on the value of the associated PDCCH identifier configuredfor each CORESET.

In some embodiments, the value of the associated PDCCH identifier is setas any one of: 0/1; on/off; or true/false.

In some embodiments, each of the M PDCCH is indicated to be monitored inall configured CORESET with the value of PDCCH identifier associatedwith the specific PDCCH is any one of: 1; on or true.

In some embodiments, a number P of PDCCH which needs to be monitored inone monitoring occasion equals to the total number of different PDCCHwhich is configured to be monitored in at least one CORESET.

In some embodiments, the at least one associated PDCCH identifier ofeach CORESET configuration is a single PDCCH identifier that indicatesthat a single PDCCH associated with a specific value of the single PDCCHidentifier is to be monitored in the CORESET.

In some embodiments, the at least one associated PDCCH identifier ofeach CORESET configuration is a single PDCCH identifier that indicatesthat a single PDCCH associated with a specific value of the single PDCCHidentifier is to be monitored in the CORESET.

In some embodiments, a single PDCCH identifier of each CORESETconfiguration is configured with one specific value out of M differentvalues, where M is an integer ≥1, which are used to indicate the maximumM PDDCH that may be monitored in at least one CORESET configured for onesearch space type.

In some embodiments, each of the M PDCCH is associated with one specificvalue of the single PDCCH identifier.

In some embodiments, M different values of the single PDCCH identifierare 1, . . . , M.

In some embodiments, each of the M PDCCH is indicated to be monitored inat least one CORESET which has the PDCCH identifier value associated forthe specific PDCCH, otherwise, the PDCCH is not monitored.

In some embodiments, a number P of PDCCH to be monitored in onemonitoring occasion equals a total number of different PDCCH which areconfigured to be monitored in at least one CORESET.

In some embodiments, the single PDCCH identifier includes one PDCCHidentifier which is common for Physical Downlink Shared Channel (PDSCH)and Physical Uplink Shared Channel (PUSCH).

In some embodiments, the single PDCCH identifier includes a PDCCHidentifier set including a specific PDCCH identifier for PDSCH and aspecific PDCCH identifier for PUSCH.

In some embodiments, a device that performs methods described above isan electronic device, such as a UE or baseband chip. A general exampleof such a device is described in FIG. 3A.

With regard to the implementation details of the CORESET configuration,reference can be made to the above-discussed embodiments, with theircombination and modification falling within the scope of the presentapplication.

Solution 1-3-1

Some embodiments of the present disclosure are related to a UEdetermining an association between PDCCH for PDSCH or PUSCH, or both,and CORESET and the number PDCCHNum of PDCCH for PDSCH and PUSCH isexplicitly indicated in addition to CORESET configuration. PDCCHNum isthe same as the variable P mentioned in the previous embodiments and iscommon to both PDSCH and PUSCH.

In some embodiments, the association between PDCCH and CORESET may bebased on a CORESET configuration including Solution 1-1 and Solution1-2-1, as described above, where P and M are always the same or equal toPDCCHNum.

In some embodiments, the association between PDCCH and CORESET can bepredefined based on one rule determined by at least one of PDCCH numberP and the number of all CORESET configured for one search space type(e.g. UE-specific). In a particular example, a predefined rule can bebased on two features. A first feature is that all CORESET may be splitinto non-overlapping P CORESET sets wherein each CORESET set with aspecific index p (e.g. 1, . . . P) has at least one CORESET, and atleast two CORESET from different CORESET sets have continuous CORESETindices and/or CORESET configuration indices. A second feature is thateach PDCCH with specific PDCCHIdx=p (e.g. 1, . . . ,P) is associatedwith specific COREST set p. This means different PDCCH can be monitoredfrom different CORESET sets. This example also implies that one PDCCHcan be monitored from all CORESET if P=1.

In some embodiments, the association between PDCCH and CORESET can bepredefined based on a mapping table determined by at least one of PDCCHnumber P and number of all CORESET configured for one search space type(e.g. UE-specific). Such a table may follow the predefined rulesmentioned in the previous embodiments.

In a particular example, when PDCCHNum=1, the UE monitors one PDCCH forPDSCH or one PDCCH for PUSCH, or both, within one or multiple CORESET.When PDCCHNum=2, the UE monitors two PDCCHs for PDSCH or two PDCCH forPUSCH, or both, within multiple CORESET based on the predefined mappingtable. Table 3 shows a non-limiting number of examples of theassociation between the PDCCHNum value and CORESET number.

TABLE 3 Relationship between on PDCCHNum value, CORESET number andPDCCH-CORESET Association PDCCHNum CORESET Number Association 1 1PDCCH1-CORESET0 1 2 PDCCH1-CORESET0 PDCCH1-CORESET1 2 2 PDCCH1-CORESET0PDCCH2-CORESET1 2 3 PDCCH1-CORESET0 PDCCH1-CORESET1 PDCCH2-CORESET2 OrPDCCH1-CORESET0 PDCCH2-CORESET1 PDCCH2-CORESET2

The example associations shown in Table 3 are non-exhaustive examplesand one skilled in the art would understand how further permutationscould be defined based on the particular examples.

In some embodiments, each PDCCH is monitored from a non-overlappingsubset of CORESET from all of the CORESET.

FIG. 19 is a flow chart describing a method according to an aspect ofthe present application. Step 1910 involves receiving a signalingincluding a Physical Downlink Control Channel (PDCCH) number (PDCCHNum,PDCCHNum ≥1) configuration. Step 1920 involves determining anassociation between the PDCCH number and at least one Control ResourceSet (CORESET). Step 1930 involves monitoring a number of PDCCH equal tothe PDCCH number in at least one CORESET within a monitoring occasionbased on the association.

In some embodiments, determining the association between the PDCCHnumber and at least one CORESET further involves receiving at least oneCORESET configuration. Each CORESET configuration of the at least oneCORESET has at least one PDCCH identifier used to indicate an associatedPDCCH to be monitored or not in the CORESET.

In some embodiments, at least one PDCCH identifier of each CORESETconfiguration refers to a number of PDCCH identifiers equal to the PDCCHnumber that is used to indicate an associated PDCCH to be monitored, ornot, in the CORESET.

In some embodiments, at least one PDCCH identifier of each CORESETconfiguration refers to a single PDCCH identifier which may beconfigured with one value out of the PDCCH number of different valuesused to indicate an associated PDCCH to be monitored, or not, in theCORESET.

In some embodiments, determining the association between the PDCCH andthe at least one CORESET further involves predefining an associationbetween PDCCH and CORESET with a specific PDCCH number and a specificCORESET number.

In some embodiments, predefining the association further involvespredefining an association rule between PDCCH and CORESET based on atleast one of: all CORESET may be split into non-overlapping P CORESETsets wherein each CORESET set with specific index p (p=1, . . . P) hasat least one CORESET and at least two CORESET from different CORESET sethave continuous CORESET index and/or CORESET configuration index; andeach PDCCH with specific PDCCH identifier (PDCCHIdx=p (p=1, . . . P)) isassociated with specific COREST set p.

In some embodiments, predefining the association further involvespredefining an association table between the PDCCH and the CORESET withPDCCH number and CORESET number based on the CORESET configuration.

In some embodiments, a device that performs methods described above isan electronic device, such as a UE or baseband chip. A general exampleof such a device is described in FIG. 3A.

With regard to the implementation details of the association, referencecan be made to the above-discussed embodiments, with their combinationand modification falling within the scope of the present application.

Solution 1-3-2

Some embodiments of the present disclosure are related to a UEdetermining the association between PDCCH for PDSCH or PUSCH, or both,and CORESET. In some implementations, the association between PDCCH forPDSCH and PUSCH and CORESET is specifically determined based on thespecific PDCCH number for PDSCH (PDCCHDLNum, i.e. P_DL) and for PUSCH(PDCCHULNum, i.e. P_UL), CORESET configuration and predefined ruleand/or table. The predefined rule and/or table can be the same as thosefor previous embodiments and common for PDSCH and PUSCH.

In a first example, with a single CORESET configuration and one PDCCHfor PDSCH and/or one PDCCH for PUSCH, the PDCCH for PDSCH and/or PUSCHmay be monitored from one CORESET if PDCCHDLNum=1 and PDCCHULNum=1. In asecond example, with two CORESET configurations and two PDCCH for PDSCHand/or two PDCCH for PUSCH, the PDCCH for PDSCH and/or the PDCCH forPUSCH may be monitored from two CORESET if PDCCHDLNum=2 andPDCCHULNum=2. In such an example, one PDCCH for PDSCH or PUSCH is onlyfrom one COREST. In a third example, with two CORESET configurations andtwo PDCCH for PDSCH, PDCCH for PDSCH may be monitored with each PDCCHfrom different CORESET if PDCCHDLNum=2 while one PDCCH for PUSCH may bemonitored from two CORESET if PDCCHULNum=1.

Each PDCCH is monitored from one subset of CORESET of all CORESET.

Solution 1-4

Some embodiments of the present disclosure are related to supporting twoseparate PDCCH monitoring configurations based on one explicitmonitoring mode configuration which is common for PDSCH and PUSCH.

A first monitoring mode may include the UE being configured to monitordifferent PDCCH from different CORESET. In this configuration the UE canmonitor one PDCCH from one CORESET subset of all configured CORESETs forone search space type. In some embodiments, the monitoring can beperformed as predefined rule and/or mapping table described above. Inother embodiments, the monitoring may be based on a mapping table asshown in Table 4 below.

A second monitoring mode may include monitoring one or multiple PDCCHfor PDSCH and/or PUSCH from all CORESET, which are configured for onesearch space type. Moreover, this monitoring mode may be one defaultconfiguration.

TABLE 4 Relationship between on PDCCHNum, CORESET number andPDCCH-CORESET PDCCHNum CORESET Number Association 2 2 PDCCH1-CORESET1PDCCH2-CORESET2 2 3 PDCCH1-CORESET1 PDCCH1-CORESET2 PDCCH2-CORESET3 OrPDCCH1-CORESET1 PDCCH2-CORESET2 PDCCH2-CORESET3

The example associations shown in Table 4 are non-exhaustive examplesand one skilled in the art would understand how further permutationscould be defined based on the particular examples.

FIG. 20 is a flow chart describing a method according to an aspect ofthe present application. Step 2010 involves receiving a signalingincluding a Physical Downlink Control Channel (PDCCH) number (PDCCHNum,PDCCHNum ≥1) configuration. Step 2020 involves receiving an indicationfor determining the PDCCH monitoring mode. In some embodiments, theindication may define which monitoring mode is to be used. For example,the indication may indicate whether a first monitoring mode is to beused or not. If the indication indicates that a first monitoring mode isnot to be used, then it is determined that a second monitoring mode isto be used. Step 2030 involves monitoring a number of PDCCH equal to thePDCCH number in at least one Control Resource Set (CORESET) within amonitoring occasion based on the determined monitoring mode.

In some embodiments, the PDCCH monitoring mode includes one of: a firstPDDCH monitoring mode that corresponds to monitoring different PDCCH indifferent CORESET for at least two PDCCH for PUSCH or at least two PDCCHfor PUSCH based on a predefined association between PDCCH and CORESET;and a second PDDCH monitoring mode corresponds to monitoring one, ormultiple, PDCCH in all CORESET that are configured for one search spacetype.

In some embodiments, the predefined association includes one of: apredefined association rule between PDCCH and CORESET; or a predefinedassociation table between PDCCH and CORESET.

With regard to the implementation details of the monitoring mode,reference can be made to the above-discussed embodiments, with theircombination and modification falling within the scope of the presentapplication.

In some embodiments, a device that performs methods described above isan electronic device, such as a UE or baseband chip. A general exampleof such a device is described in FIG. 3A.

Solution 2-1

Some embodiments of the present disclosure are related to determiningscrambling information used to scramble a portion of a communicationbased on one PDCCH identity/index (i.e. for example the PDCCHIdxmentioned in previous embodiments). This determining can be predefinedor configured for the UE.

In some implementations, PDCCH identity (PDCCHIdx) may be used togenerate a scrambling initialization value. For example, thisinitialization value may be defined as c_(init) shown below for PDSCHscrambling. An example of a c_(int) for PDSCH or PUSCH is

c ^(init) =n _(RNTI)*2¹⁴ +q*2¹³ +[n _(s)/2]*2⁹ +N _(ID) ^(cell)

where in q can be codeword index for one PDCCH or can be PDCCH identityfor multiple PDCCH;

-   -   In this example, the initialization value can be used for        scrambling a channel which is at least one of PDSCH or PUSCH.        This implies that different PDCCHIdx can be used to scramble        different channels that are associated with a PDCCH identified        with PDCCHIdx.

Solution 3-1

Some embodiments of the present disclosure are related to the UEdetermining a single PUCCH resource that can be used by the UE that isassociated with multiple PDCCH/PDSCH that may be used by one or multiplerespective transmission points.

FIG. 14 illustrates an example scenario in which two TRPs 1410 and 1420are communicating with a single UE 1430. TRP 1410 is communicating inthe DL direction on beam 1415 using PDCCH/PDSCH allocated for TRP 1410.TRP 1420 is communicating in the DL direction on beam 1425 usingPDCCH/PDSCH allocated for TRP 1420. The UE 1430 communicates with bothTRPs 1410 and 1420 in the UL direction using beam 1435. PUCCH used bythe UE 1430 occurs over beam 1435 and each TRP 1410 and 1420 needs to beable to decode the portion of the PUCCH relevant to the respective TRP.

The UE may determine the single PUCCH resource information, which is atleast one of time resource information, frequency resource information,code or sequence resource information, frequency-hopping pattern andtransmission beam information, or any subset thereof. Time resourceinformation that can include at least one of: a starting symbol index; asymbol duration within a slot; an ending symbol index; a starting slotindex; a slot duration and an ending slot index. Frequency resourceinformation than can include at least one of: a starting physicalresource block (PRB) index; a PRB number for one PUCCH and an ending PRBindex. Code or sequence resource information that can include at leastone of orthogonal cover code (OCC) index and cyclic shift index. Afrequency-hopping pattern. Transmission beam information that caninclude at least one of: UL Beam Pair Link (BPL), QCL assumption betweenDMRS of PUSCH with another DL RS which can be at least one of CSI-RS, SSblock and DMRS for associated PDCCH, DMRS for associated PDSCH.

Any PUCCH resource information can be received by a RRC signaling and/ora specific DCI. A specific DCI might be selected from multiple PDCCHbased on one predefined rule. For example, a PDCCH with the lowestIdentity/index (i.e. PDCCH1) will be selected. A specific DCI might beselected from one of the multiple PDCCH by receiving another RRCsignaling indicating PDCCH Identity/index which is used for PDCCHselection.

The UE determining a PUCCH format (e.g. long or short) for a singlePUCCH can be determined based on a combination of multiple uplinkcontrol information (UCI) feedback associated with multiple PDCCH/PDSCHwherein each UCI feedback is associated with one specific PDCCH/PDSCHand each UCI includes at least one of ACK/NACK, channel qualityinformation (CQI), Pre-coding Matrix indicator (PMI), rank indicator(RI), scheduling request (SR). In a first example, the determination canbe based on the UCI combination type, in which a first PUCCH format canbe for ACK/NACK and/or SR and a second PUCCH format can be for any oneor more of an ACK/NACK SR, or CSI report (e.g. CQI/PMI/RI/SRI, etc.). Ina second example, the determination can be based on the payload size(i.e. total bit number) for a UCI combination. In such an example, afirst PUCCH format can be used for UCI combination with payload sizeless than one threshold number; otherwise second PUCCH format can beused.

FIG. 21 is a flow chart describing a method according to an aspect ofthe present application. Step 2110 involves receiving multiple PhysicalDownlink Control Channels (PDCCHs) or Physical Downlink Shared Channel(PDSCHs), or both. Step 2120 involves transmitting a single PhysicalUplink Control Channel (PUCCH) for the transmission of a combination ofmultiple uplink control information (UCI) feedback, wherein each UCIfeedback is associated with at least one of one specific PDCCH and onespecific PDSCH.

In some embodiments, the method further involves determining the singlePUCCH resource.

In some embodiments, the single PUCCH resource includes at least one of:a time resource; a frequency resource; a code or sequence resource; afrequency hopping pattern; a transmission beam; and a PUCCH format.

In some embodiments, a device that performs methods described above isan electronic device, such as a UE or baseband chip. A general exampleof such a device is described in FIG. 3A.

With regard to the implementation details of the PUCCH and UCI,reference can be made to the above-discussed embodiments, with theircombination and modification falling within the scope of the presentapplication.

Solution 3-2

Some embodiments of the present disclosure are related to the UEdetermining multiple PUCCH resources for the transmission of multiplePUCCH associated with multiple PDCCH/PDSCH. In some implementations,each PUCCH resource is associated with one specific PDCCH/PDSCH. Forexample, the PUCCH may be associated with a specific PDCCH identity.

FIG. 14 described above was directed to a single beam being used for acommon PUCCH for multiple TRPs. An alternative to such an approachinvolves using separate PUCCH for each of two or more TRPs. FIGS. 15A to15F illustrate six different non-limiting examples of separate PUCCHresource configurations.

In FIG. 15A, a UE determines multiple PUCCH resources for thetransmission of multiple PUCCH, where each PUCCH is associated to arespective PDCCH/PDSCH and each PUCCH uses a separate PUCCH format. Fora given slot, two separate PDCCH 1500, 1510 are shown. Each PDCCH may beconsidered a time-frequency resource. A portion of each PDCCH 1500, 1510is allocated for a PUCCH 1508, 1518 associated with the respective PDCCH1500, 1510. The contents of each PUCCH 1508, 1518 is transmitted on arespective beam 1504, 1514 from the UE to a respective TRP, using arespective PUCCH format.

In FIG. 15B, a UE determines multiple PUCCH resources for thetransmission of multiple PUCCH, where each PUCCH is associated to arespective PDCCH/PDSCH and each PUCCH is transmitted in one or multipleslots. Two separate PDCCHs 1520, 1530 are shown, each associated with aseparate slot. Associated with each PDCCH 1520, 1530 is a respectivePUCCH 1528, 1538. The contents of each PUCCH 1528, 1538 is transmittedon a respective beam 1524, 1534 from the UE to a respective TRP.

In FIG. 15C, a UE determines multiple PUCCH resources for thetransmission of multiple PUCCH, where each PUCCH is associated to arespective PDCCH/PDSCH and each PUCCH is transmitted in one or multipleslots. Two separate slots are shown in which a first PUCCH 1540 occupiesa portion of the resources of both slots and a second PUCCH 1542occupies a portion of the resources of only one slot of the two slots.For example, the only one slot may be the first slot. In someimplementations (not shown in FIG. 15C), the second PUCCH 1542 mayoccupy a portion of the resources of both slots. It is understood thetwo slots as shown in FIG. 15C are only examples for the purpose ofillustration, this embodiment may apply to more than two slots.

In FIG. 15D, a UE determines multiple PUCCH resources for thetransmission of multiple PUCCH, where each PUCCH is transmitted in asingle slot on a separate beam that is derived from the QCL associationbetween the PUCCH DMRS and a respective CSI-RS. For a single slot, twoseparate CSI-RS 1550, 1560 are shown. Associated with each CSI-RS 1550,1560 is a respective PUCCH 1558, 1568. The content of each PUCCH1558,1568 is transmitted on a respective beam 1554, 1564 from the UE toa respective TRP.

In FIG. 15E, a UE determines multiple PUCCH resources for thetransmission of multiple PUCCH, where each PUCCH is transmitted in asingle slot on a separate beam that is derived from the QCL associationbetween the PUCCH DMRS and a respective PDCCH DMRS. For a given slot,two separate PDCCH-DMRS 1570, 158 o are shown. Associated with eachPDCCH-DMRS 1570, 1580 is a respective PUCCH 1578, 1588. The content ofeach PUCCH 1578, 1588 is transmitted on a respective beam 1574, 1584from the UE to a respective TRP.

In FIG. 15F, a UE determines multiple PUCCH resources for thetransmission of multiple PUCCH, where each PUCCH is transmitted in asingle slot on a separate beam that is derived from the QCL associationbetween the PUCCH DMRS and a respective PDSCH DMRS. For a given slot,two separate PDSCH-DMRS 1590, 1595 are shown. Associated with eachPDSCH-DMRS 1590, 1595 is a respective PUCCH 1594, 1599. The contents ofeach PUCCH 1594, 1599 is transmitted on a respective beam 1592, 1597from the UE to a respective TRP.

While FIGS. 15A to 15F are described with regard to a slot, it is to beunderstood that this is one example of a time duration. More generally,the time duration could be an OFDM symbol, a group of OFDM symbols, amini-slot, a subslot (a shorter duration than a slot) or multiple slots

The UE determining multiple PUCCH resource information in which each ofthe multiple PUCCH resource information associated with one specificPDCCH/PDSCH is based on sub-resource information, which is at least oneof time resource information, frequency resource information, code orsequence resource information, frequency-hopping pattern andtransmission beam information. Time resource information which caninclude at least one of: a starting symbol index; a symbol durationwithin a slot; a starting symbol index; a starting slot index; and aslot duration and an ending slot index. Frequency resource informationwhich can include at least one of: PRB index; PRB number for one PUCCHand bandwidth part index. Code or sequence resource information whichcan include at least one of OCC index and cyclic shift index. Afrequency-hopping pattern. Transmission beam information which caninclude at least one of UL BPL; QCL assumption between DMRS of PUCCHwith another DL RS which can be at least one of CSI-RS; SS block andDMRS for associated PDCCH; and DMRS for associated PDSCH.

Any sub-resource information can be configured by receiving RRCsignaling or a DCI. Some sub-resource information configured byreceiving RRC signaling may be shared between multiple PUCCH resourceinformation. For example, frequency resource information can be sharedfor multiple PUCCH resources. Some sub-resource information configuredby DCI may be received from specific PDCCH, for example, transmissionbeam information for first PUCCH resource information can be from firstPDCCH while transmission beam information for second PUCCH resourceinformation can be from second PDCCH.

In some implementations, multiple PUCCH resources may share at least onecommon resource information (e.g. starting slot index, frequency-hoppingpattern) that are discussed above. The at least one common resourceinformation may be configured with RRC and common for multiple PUCCH.

Specific PUCCH format (e.g. long or short) for multiple PUCCH can bedetermined based on specific uplink control information (UCI) feedbackassociated with specific PDCCH/PDSCH, wherein each UCI feedback includesat least one of ACK/NACK, CQI, PMI, RI, and SR.

FIG. 22 is a flow chart describing a method according to an aspect ofthe present application. Step 2210 involves receiving multiplerespective Physical Downlink Control Channels (PDCCHs) or PhysicalDownlink Shared Channels (PDSCHs), or both. Step 2220 involvestransmitting multiple Physical Uplink Control Channels (PUCCHs) for thetransmission of multiple uplink control information (UCI) feedback,wherein each UCI feedback is associated with at least one of onespecific PDCCH and one specific PDSCH.

In some embodiments, the method further involves determining themultiple PUCCH resources.

In some embodiments, the single or multiple PUCCH resources include atleast one of: a time resource; a frequency resource; a code or sequenceresource; a frequency hopping pattern; a transmission beam; and a PUCCHformat.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH use the same or differentPUCCH format.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH are located in a single slot,such that each PUCCH's starting OFDM symbol is located in a single slotand its duration is less than or equal to the duration of a slot.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH are located in multiple slots,such that each PUCCH's starting OFDM symbol is located in a single slotand its duration is less than, equal to, or longer than, the duration ofa slot.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH are located in multiple slots,such that each PUCCH's ending OFDM symbol is located in a single slotand its duration is less than, equal to, or longer than, the duration ofa slot.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH are located in separate slots,such that each PUCCH's starting OFDM symbol is located in a given slotand its duration is less than or equal to the duration of a slot.

In some embodiments, the multiple PUCCH resources used for thetransmission of multiple respective PUCCH use respective transmissionbeams that are derived using the quasi-collocated association between arespective PUCCH Demodulation Reference Signal (DMRS) and a respectiveDownlink Reference Signal (DL RS).

In some embodiments, the DL RS is a Channel State Information—ReferenceSignal (CSI-RS). In some embodiments, the DL RS is a PDCCH DMRS. In someembodiments, the DL RS is a PDSCH DMRS.

In some embodiments, resource information pertaining to the single ormultiple PUCCH resource is configured with at least one of: RRCsignaling; Downlink Control Information (DCI); Media Control AccessControl Element (MAC CE); and a predefined rule.

In some embodiments, the method may further comprise: determining aPUCCH feedback mode; and transmitting a single or multiple PUCCH basedon the PUCCH feedback mode.

In some embodiments, the determining the PUCCH feedback mode is made byselecting one of two separate feedback modes.

In some embodiments, a first mode is for a single PUCCH and a secondmode is for multiple PUCCH.

In some embodiments, determining the PUCCH feedback mode comprisesmaking a determination based on an implicit mechanism using a PDCCH toCORESET association.

In some embodiments, determining the PUCCH feedback mode comprisesreceiving a higher-layer signaling.

In some embodiments, the higher-layer signaling includes at least oneof: RRC signaling; Downlink Control Information (DCI); and Media ControlAccess Control Element (MAC CE).

In some embodiments, one or more of the above described embodiments maybe combined.

In some embodiments of the methods described above for Solutions 3-1 and3-2, resource information pertaining to the single or multiple PUCCHresource is configured with at least one of: RRC signaling; DownlinkControl Information (DCI); Media Control Access Control Element (MACCE); and a predefined rule.

In some embodiments of the methods described above for Solutions 3-1 and3-2, the method further involves: determining a PUCCH feedback mode; andtransmitting a single or multiple PUCCH based on the PUCCH feedbackmode.

In some embodiments, the determination is made by selecting one of twoseparate feedback modes.

In some embodiments, a first mode is for a single PUCCH; and a secondmode is for multiple PUCCH.

In some embodiments, determining the PUCCH feedback mode comprisesmaking a determination based on an implicit mechanism using a PDCCH toCORESET association.

In some embodiments, determining the PUCCH feedback mode comprisesreceiving a higher-layer signaling.

In some embodiments, the higher-layer signaling includes at least one ofRRC signaling, Downlink Control Information (DCI), and Media ControlAccess Control Element (MAC CE).

In some embodiments, a device that performs methods described above isan electronic device, such as a UE or baseband chip. A general exampleof such a device is described in FIG. 3A.

With regard to the implementation details of PUCCH and UCI, referencecan be made to the above-discussed embodiments, with their combinationand modification falling within the scope of the present application.

Solution 3-3

Some embodiments of the present disclosure are related to the UEdetermining a PUCCH feedback mode, also known as a report mode. In someimplementations, the determination may be made between two separatemodes. A first mode (Mode 1) may be for a single PUCCH a second mode(Mode 2) may be for multiple PUCCH. In some embodiments, thedetermination may be made based on an explicit RRC configuration. Theexplicit RRC configuration may be in conjunction with the CORESETconfiguration.

In some embodiments, the determination may also be made implicitly basedon the CORESET configuration that is defined with RRC signaling or apredefined mapping table. A non-limiting example of a mapping table isshown in Table 5 below.

TABLE 5 Relationship between PDCCHNum value, CORESET number,PDCCH-CORESET Association and PUCCH mode CORESET PUCCH PDCCHNum NumberAssociation mode 1 1 PDCCH1-CORESET0 Mode1 1 2 PDCCH1-CORESET0 Mode1PDCCH1-CORESET1 2 1 PDCCH1-CORESET0 Mode1 PDCCH2-CORESET0 2 2PDCCH1-CORESET0 Mode2 PDCCH2-CORESET1 2 3 PDCCH1-CORESET0 Mode2PDCCH1-CORESET1 PDCCH2-CORESET2 Or PDCCH1-CORESET0 PDCCH2-CORESET1PDCCH2-CORESET2

In some embodiments, Mode1 is the PUCCH feedback mode to be used by theUE for the following cases: single PDCCH received on a single CORESET;single PDCCH received on multiple CORESETs; or multiple PDCCHs receivedon a single CORESET. Mode 2 is the PUCCH feedback mode selected by theUE for all other cases.

The example associations shown in Table 5 are non-exhaustive examplesand one skilled in the art would understand how further permutationscould be defined based on the particular examples.

Solution 4-1

Some embodiments of the present disclosure are related to the UEdetermining multiple CSI-RS configurations sent from the network andthen reporting multiple CSI-RS based measurements over separate PUSCH tothe network based on an association between one PUSCH and one ormultiple CSI-RS configurations.

In some embodiments, the association between one PUSCH and one ormultiple CSI-RS configurations may be received by the UE in a high-layersignaling, e.g., a RRC signaling. For example, multiple CSI-RSconfigurations will be divided into multiple CSI-RS configuration groups(one CSI-RS configuration group includes at least one CSI-RSconfiguration), then a measurement for one CSI-RS configuration groupcan be reported with one specific PUSCH based on the association. (e.g.PUSCH1 for CSI-RS configuration group1 and PUSCH2 for CSI-RSconfiguration group2).

In some embodiments, the association between one PUSCH and one ormultiple CSI-RS configurations may be implicitly derived by the UE. Theimplicit derivation can be based on a QCL assumption between a specificDMRS of PDCCH and one particular CSI-RS configuration. For example, DMRSof PDCCH1 for PUSCH1 may be quasi co-located with CSI-RS1 configurationwhile DMRS of PDCCH2 for PUSCH2 may be quasi co-located with CSI-RS2configuration. Then measurement of CSI-RS1 can be reported with PUSCH1and measurement of CSI-RS2 can be reported with PUSCH2 based on theassociation as explained above. It is understood that multiple CSI-RSconfigurations in one CSI-RS configuration group may be associated withone PUSCH.

FIG. 16A illustrates a representation of two groups of one or more CSIconfigurations 1610 and 1620 each being associated with a respectivePUSCH, one group with PUSCH1 1615 and one group with PUSCH2 1625.

FIG. 16B illustrates a representation of two groups of one or more CSIconfigurations 1630 and 1640 each being associated with a respectivePDCCH, PDCCH1 1633 and PDCCH2 1643, based on a QCL assumption.PDCCH11633 and PDCCH2 1643 are respectively associated with PUSCH1 1635and PUSCH2 1645.

FIG. 23 is a flow chart describing a method according to an aspect ofthe present application. Step 2310 involves determining an associationbetween multiple Channel State Information—Reference Signal (CSI-RS)configurations and multiple Physical Uplink Control Channel (PUSCH).Step 2320 involves reporting one or multiple CSI-RS measurement over anassociated separate PUSCH based on the association between multipleCSI-RS configuration and multiple PUSCH.

In some embodiments, determining the association comprises receiving asignaling indicating the association.

In some embodiments, determining the association involves determining aCSI-RS configuration that is associated with a PUSCH which is scheduledby a PDCCH, the PDCCH being associated with a DMRS quasi co-located witha CSI-RS.

In some embodiments, a device that performs methods described above isan electronic device, such as a UE or baseband chip. A general exampleof such a device is described in FIG. 3A.

With regard to the implementation details of the association, referencecan be made to the above-discussed embodiments, with their combinationand modification falling within the scope of the present application.

FIG. 24A illustrates an example of a cell 2400 with two TRPs 2402 and2404. There are three UEs 2412, 2414, 2416 being served within the cell2400. UE 2412 is allocated a DL assignment 2421 and an uplink assignment2422 by TRP 2402 and by downlink assignment 2423 by TRP 2404. UE 2414 isallocated a DL assignment 2424 and an uplink assignment 2425 by TRP2404. UE 2416 is allocated a DL assignment 2426 and an uplink assignment2427 by TRP 2404. In this particular example, two TRPs are transparently(from the UE perspective) associated with two separate CORESET groups(also two CORESETs) configured for a single UE.

FIG. 24B illustrates an example of the DL and UL assignments for UE 2412from each of TRP 2402 and TRP 2404. The assignments from TRP 2402 arefor DL and UL as shown in FIG. 24A and include four candidate numbers(CN), in this particular example. The assignments from TRP 2404 are forDL only as shown in FIG. 24A and include two candidate numbers, in thisparticular example. In this particular example, two TRPs aretransparently associated with two separate CORESET groups (also twoCORESETs) configured for one UE. Each PDCCH is associated with aspecific CORESET which is associated with a different search space withdifferent candidate numbers (2 and 4 in the figure) for a sameaggregation level.

Table 6 illustrates an example that defines multiple search spaces (bothaggregation level and candidate number) for EPDCCH candidates and forNR-PDCCH candidates associated with two different CORESETs (alsogenerally corresponding to two CORESET groups). The contents of the rowsand columns are as defined above for Table 2. The values in the CORESET1 and CORESET2 columns of Table 6 represent the number of PhysicalResource Blocks (PRB) used in the CORESET.

TABLE 6 Number of candidates for different aggregation levels fordifferent CORESETS Number of EPDCCH candidates Number of NR-PDCCHcandidates for two CORESETs for two CORESETs CORESET1 CORESET2 L = 1 L =2 L = 4 L = 8 L = 16 L = 1 L = 2 L = 4 L = 8 L = 16 2 2 4, 4 2, 2 1, 10, 0 0, 0 4, 4 2, 2 1, 1 0, 0 0, 0 4 4 3, 3 3, 3 1, 1 1, 1 0, 0 3, 3 3,3 1, 1 1, 1 0, 0 8 8 3, 3 2, 2 1, 1 1, 1 1, 1 4, 2 4, 2 2, 1 2, 1 2, 1 42 5, 3 3, 2 1, 1 1, 0 0, 0 4, 2 4, 2 2, 1 1, 1 0, 0 8 2 4, 2 4, 2 1, 11, 0 1, 0 2, 4 2, 4 1, 2 1, 1 1, 1 8 4 3, 3 2, 2 2, 1 1, 1 1, 0 3, 3 2,2 2, 1 1, 1 1, 0

In some implementations, for different CORESETs that may be monitored bya UE, the configuration information provided to the UE for eachpotential CORESET may have the same aggregation level (AL) setassociated with non-zero CN for each AL, i.e. {1,2,4,8,16}. For the sameaggregation level, the CN can be independently configured for eachCORESET. In a first example, different CORESETs with a same size (timeresource and/or frequency resource) can be configured with different CNfor the same aggregation level. In a second example, a first CORESETwith a smaller size can be configured for a larger CN and a secondCORESET with a larger size can be configured for a smaller CN for thesame aggregation level. In a third example, for a specific aggregationlevel AL, associated candidate number CN_AL is determined by onepredefined CN_ALo and the configured total number of PDCCH (N_PDCCH) forPUSCH and/or PDSCH which can be simultaneously detected or received fromthe associated the specific CORESET in the form CN_AL=CN_ALo*N_PDCCH.

Referring back to Table 6, there are several aspects pertaining to thecandidate numbers that should be noted.

For example, in the third row it is noted that CORESET1 has 8 PRB andCORESET2 has 8 PRB. The number of the candidates (CN) for the EPDCCHscenario for L=1 is 4 for CORESET1 and 4 for CORESET2. In this case, theCN for the two CORESETs are equal. The same is shown for L=2, 4, 8 and16, even though the number of candidates decreases with increasingaggregation level. However, in the NR-PDCCH scenario, the CN for L=2 isequal to 4 for CORESET1 and equal to 2 for CORESET2. The CN for thedifferent CORESETs with same size is different.

In the fifth row it is noted that for L=1 CORESET1 has 8 PRB andCORESET2 has 2 PRB. The number of the candidates (CN) for the EPDCCHscenario for L=1 is 4 for CORESET1 and 2 for CORESET2. In this case theCORESET with the larger number of PRBs also has the large CN. However,in the NR-PDCCH scenario, the CN is equal to 2 for CORESET1 and equal to4 for CORESET2. Therefore, the CORESET with the larger number of PRBshas the smaller CN.

As can be seen by at least the two above examples from Table 6, thecandidate number for the NR-PDCCH scenarios can be independent of theCORESET size.

In implementations of the present application, the maximum PDCCH numberfor all channels within each CORESET may be different. Each CORESET canbe shared by a different UE or by different groups of UEs. For example,referring back to FIG. 24A, for UE 2412, a first CORESET (CORSET1) isused for both UL and DL assignment as allocated by TRP 2402 and a secondCORESET (CORSET2) is used for only for DL assignment as allocated by TRP2404. In such a scenario, CORESET1 likely has a larger CN than CORESET2to accommodate that CORESET1 is providing assignment for both UL and DL.However, for UE 2414, CORESET2 is used for both UL and DL assignment asallocated by TRP 2404.

Table 6 is again merely an example of candidate numbers for respectiveaggregation levels for CORESTS of same and/or different sizes that wouldbe consistent with the present application. It is to be understood thatthese are example values and are not intended to be limiting in nature.

Assignment Number Specific Search Space Splitting

In some implementations, a case specific search space has aconfiguration that is different with respect to a maximum number ofPDCCH a UE is configured to monitor for one data channel type (unicastor UE-specific) and one RNTI type of one cell within one same monitoringoccasion. A configuration for each case specific search space definesthe association among a given CORESET and for a given aggregation leveland candidate number. Various examples are shown in Table 7 below.

TABLE 7 Number of candidates for different aggregation levels fordifferent size CORESETS for one and two assignment scenarios Number ofPDCCH candidates Number of PDCCH candidates for one assignment case fortwo assignment case CORESET1 CORESET2 L = 2 L = 4 L = 8 L = 16 L = 32 L= 1 L = 2 L = 4 L = 8 L = 16 2 2 4, 4 2, 2 1, 1 0, 0 0, 0 6, 6 3, 3 2, 20, 0 0, 0 4 4 3, 3 3, 3 1, 1 1, 1 0, 0 6, 6 3, 3 2, 2 1, 1 0, 0 8 8 3, 32, 2 1, 1 1, 1 1, 1 3, 3 2, 2 2, 1 1, 1 1, 1 4 2 5, 3 3, 2 1, 1 1, 0 0,0 5, 3 3, 2 2, 1 2, 1 0, 0 8 2 4, 2 4, 2 1, 1 1, 0 1, 0 4, 2 4, 2 1, 11, 2 1, 1 8 4 3, 3 2, 2 2, 1 1, 1 1, 0 3, 5 2, 2 2, 1 1, 1 1, 1

Purely by way of example, a UE may be provided with all of theinformation in Table 7. In a scenario in which the UE is to operate foronly one assignment, the UE can use the pertinent information in theportion of Table 7 defining the number of candidates for the oneassignment case. In a scenario in which the UE is to operate for twoassignments, the UE can use the pertinent information in the portion ofTable 7 defining the number of candidates for the two assignment case.

Table 7 is again merely an example of candidate numbers for respectiveaggregation levels for CORESTS of same and/or different sizes fordifferent number of assignments that would be consistent with thepresent application. While example AL and CN information is provided forone and two assignment scenarios, it is to be understood that similarinformation may be provided to the UE for scenarios with a larger numberof assignments than two. It is to be understood that these are examplevalues and are not intended to be limiting in nature.

In some implementations, configuration sets associated with CORESETShaving defined aggregation levels and candidate numbers that are beingused for existing communication standards may be used as a defaultconfiguration sets, for example for a one assignment case, to ensurecompatibility with existing systems.

Time Resource Information for Specific Case

Time resource information for multiple PDCCHs and/or associated PDSCHsand/or PUSCHs and/or PUCCHs from one or more TRPs for a single datachannel type (unicast or UE-specific) can be the same or different.

In some implementations, the UE is configured with different indicationsfor different time resource information for different PDCCH and/or otherassociated channels and each indication is associated with one specifictime resource information. In a first example, in which there are twoPDCCH (PDCCH1 and PDCCH2), the starting symbol and/or ending symbol forPDCCH1 and PDCCH2 can be different. In a second example in which thereare two PDCCH (PDCCH1 and PDCCH2) and associated PDSCH (PDSCH1 andPDSCH2), the starting symbol and/or ending symbol for PDSCH1 associatedwith PDCCH1 and for PDSCH2 associated with PDCCH2 can be different. In athird example in which there are two PDCCH (PDCCH1 and PDCCH2) andassociated PUSCH (PUSCH1 and PUSCH2), the starting symbol and/or endingsymbol for PUSCH1 associated with PDCCH1 and for PUSCH2 associated withPDCCH2 can be different. In a fourth example, in which there are twoPDCCH (PDCCH1 and PDCCH2) and associated PUCCH (PUCCH1 and PUCCH2), thestarting symbol and/or ending symbol for PUCCH1 associated with PDCCH1and for PUCCH2 associated with PDCCH2 can be different. Table 8 belowillustrates an association for a first PDCCH (PDCCH1) and for a secondPDCCH (PDCCH2) with other channel types.

TABLE 8 Association between multiple PDCCH and PDSCH and/or PUSCH and/orPUCCH PDCCH1 PDSCH1 PUSCH1 PUCCH1 PDCCH2 PDSCH2 PUSCH2 PUCCH2

FIG. 25A illustrates an example of a different time resource informationfor different PDCCH and associated PDSCH. FIG. 25A illustrates a PDCCH12502 with a corresponding PDSCH1 2504 occupying at least a portion of atime unit and a PDCCH2 2512 with a corresponding PDSCH2 2514 occupyingat least a portion of the time unit. While the overall duration ofPDCCH1 2502 and PDSCH1 2504 is the same for PDCCH2 2512 and PDSCH2 2514,the duration and ending symbol of the respective PDCCH(s) are differentand the duration and starting symbol of the respective PDSCHs aredifferent.

In some implementations, the UE is configured to determine the timeresource information for different PDCCHs and/or associated PDSCH and/orPUSCH and/or PUCCH. The time resource information can be based on anindication scheme. As a particular example, a first time resourceinformation can be derived from a first indication scheme and a secondtime resource information can be derived from a second indicationscheme.

General examples of indication schemes may include dynamic DL controlsignaling and semi-static RRC signaling used by the network. Specificexamples of combinations of indication schemes may include dynamiccontrol indication (DCI) and semi-static RRC signaling, a firstsemi-static RRC signaling and a second semi-static RRC signaling, and afirst DCI and a second DCI.

Time Resource Information for Common Case

In some implementations, the UE is configured with same time resourceinformation with one common indication for different PDCCH and/or otherassociated channels. In a first example in which there are two PDCCH(PDCCH1 and PDCCH2), the starting symbol and/or ending symbol for PDCCH1and PDCCH2 can be same. In a second example in which there are two PDCCH(PDCCH1 and PDCCH2) and associated PDSCH (PDSCH1 and PDSCH2), thestarting symbol and/or ending symbol for PDSCH1 associated with PDCCH1and for PDSCH2 associated with PDCCH2 can be same. In a third example inwhich there are two PDCCH (PDCCH1 and PDCCH2) and associated PUSCH(PUSCH1 and PUSCH2), the starting symbol and/or ending symbol for PUSCH1associated with PDCCH1 and for PUSCH2 associated with PDCCH2 can besame. For fourth example, the starting symbol and/or ending symbol forPUCCH1 associated with PDCCH1 and PUCCH2 associated with PDCCH2 can besame.

FIG. 25B illustrates an example of same time resource information. FIG.25B illustrates a PDCCH1 2522 with a corresponding PDSCH1 2524 occupyingat least a portion of a time unit and a PDCCH2 2532 with a correspondingPDSCH2 2534 occupying at least a portion of the time unit. The overallduration of PDCCH1 2522 and PDSCH1 2524 is the same as for PDCCH2 2532and PDSCH4 2534 and the duration and starting symbol of the respectivePDCCHs and PDSCH are the same as well.

In some implementations, the UE is configured to determine time resourceinformation that is common for multiple PDCCHs and/or associated PDSCHsand/or PUSCHs and/or PUCCHs. The time resource information can bedefined or shared based on a common indication scheme. The indicationscheme may include DL control signaling or semi-static RRC signalingused by the network.

For either the case of a different or a common time resource used bydifferent PDCCHs and/or associated PDSCHs and/or PUSCHs and/or PUCCHs, alist of examples of time resource information, which is not intended tobe limiting in nature, includes information such as PDCCH startingsymbol, PDCCH ending symbol, PDSCH starting symbol, PDSCH ending symbol,PUSCH starting symbol, PUSCH ending symbol, PUCCH starting symbol, andPUCCH ending symbol.

HARQ Feedback

When using HARQ feedback an uplink control channel is assigned to allowthe UE a channel for providing an acknowledgement or negativeacknowledgement (ACK/NACK) as to whether information (codeword and/orcode block and/or code block group) transmitted in the downlinkdirection was received and decoded. In some implementations according tothe present application, one common Physical Uplink Control Channel(PUCCH) is allocated for transmission of all ACK/NACK bits that areassociated with multiple PDCCHs and/or PDSCHs and with one PDCCH and/orPDSCH that is associated with one or multiple codewords (CW) of PDSCHand with one CW that is associated with one or multiple code blocks (CB)or code block groups (CBG) of PDSCH, wherein one CBG includes at leastone CB. An example of this is illustrated in FIG. 26A. FIG. 26Aillustrates, similarly to FIG. 25B an example of a transmission resourceincluding PDCCH1 2608A being transmitted along with PDSCH1 2609A from afirst TRP and PDCCH2 2608B being transmitted along with PDSCH2 2609Bfrom a second TRP. Also included in FIG. 26A is a single common PUCCH2605 for transmission of ACK/NACK bits associated with PDSCHs 2609A and2609B.

The total number of combined ACK/NACK bits may be determined based onone or more of the following three numbers wherein the first number isthe number of semi-statically configured maximum PDCCHs and the secondnumber is the number of semi-statically configured CWs or transportblocks (TB) associated with the specific PDCCH and the third number isthe number of semi-statically configured code blocks (CB) or code blockgroups (CBG) associated with the specific CB/TB and specific PDCCH. Oneor more CB or CBG form a codeword, as can be seen in the example of FIG.27 . In a first example, the total number of combined ACK/NACK bits isthe same as the number of PDCCH and one PDCCH is associated with oneCW/TB ACK/NACK bit. In a second example, the total number of combinedACK/NACK bits is the same as the total number of CW/TB associatedmultiple PDCCHs and one PDCCH is associated with a specific number ofCW/TB ACK/NACK bit. In a third example, the total number of combinedACK/NACK bits is the same as the total number of CB/CBG associatedmultiple PDCCHs and one PDCCH is associated with a specific number ofCB/TB and one CW/TB is associated with a specific number of CB/CBGACK/NACK bit.

FIG. 27 illustrates examples of three numbers for two successiveACK/NACK segments for two assignments (i.e. PDCCHs) associated allfeedback bits each having a respective assignment identity. For a firstscenario, the first ACK/NACK segment 2702 is associated with a firstassignment identity and the second ACK/NACK segment 2704 is associatedwith a second assignment identity. Each assignment identity has anassociated index number, i.e. Assignment Identity1 and AssignmentIdentity2. As indicated above, the number of assignments associated withthe respective ACK/NACK segments 2702 and 2704 can be used to determinethe number of ACK/NACK bits that will be concatenated together andtransmitted on the PUCCH.

For a second scenario, the first ACK/NACK segment 2702 is shown to havetwo codewords 2712 and 2714. Similarly, in the second ACK/NACK segment2704 there are two codewords 2722 and 2724. Each respective codeword hasan associated index number, i.e. CW1 and CW2, in the respective ACK/NACKsegment. As indicated above, the number of codewords in the respectiveACK/NACK segments can be used to determine the number of ACK/NACK bitsthat will be concatenated together and transmitted on the PUCCH.

For a third scenario, the first ACK/NACK segment 2702 is shown to havefour codeblocks or codeblock groups 2732, 2734, 2736 and 2738.Similarly, in the second ACK/NACK segment 2704 there are four codeblocksor codeblock groups 2742, 2744, 2746 and 2748. Each respective codeblockor codeblock group has an associated index number i.e. CB/CBG1, CB/CBG2in within each codeblock or codeblock group of the respective ACK/NACKsegment. As indicated above, the number of codeblock or codeblock groupin the respective ACK/NACK segments can be used to determine the numberof ACK/NACK bits that will be concatenated together and transmitted onthe PUCCH.

In some embodiments, the ACK/NACK bit codebook size is associated withthe maximum number of PDCCH.

If the ACK/NACK bits for multiple assignments are transmitted togetherin the PUCCH, there is to be an agreed upon manner of concatenating theACK/NACK bits to ensure that both the network and the UEs know how theACK/NACK bits are combined and thus which bits correspond to whichassignments. The manner in which the PUCCH ACK/NACK bits areconcatenated may be based on at least one of the following ordering andmapping rules for arranging the ACK/NACK bits.

In some embodiments, for ACK/NACK bits that correspond to differentassignments as shown in FIG. 27 , the ACK/NACK bits corresponding to anassignment with a lower index number precede the ACK/NACK bitscorresponding to an assignment with a higher index number.

In some embodiments, for ACK/NACK bits corresponding to one assignment,the ACK/NACK bits corresponding to a codeword with a lower index numberprecede the ACK/NACK bits corresponding to a codeword with a higherindex.

In some embodiments, for ACK/NACK bits corresponding to one codeword,the ACK/NACK bits corresponding to a code block or code block group witha lower index precede the ACK/NACK bits corresponding to the code blockor code block group with a higher index.

The UE can be provided with the common PUCCH resource for theconcatenated ACK/NACK bits via semi-static dedicated signaling, such asRRC. The resource can be at least one of a time resource, a frequencyresource, a combination time/frequency resource, a code, a layer andport resource.

In another implementation, as shown in FIG. 26B, separate PUCCH(s) aretransmitted for ACK/NACK bits that are associated with differentassignments. FIG. 26B illustrates an example of a transmission resourceincluding PDCCH1 2618A being transmitted along with PDSCH1 2619A from afirst TRP and PDCCH2 2618B being transmitted along with PDSCH2 2619 bfrom a second TRP. Also included in FIG. 26B are two PUCCH, PUCCH1 2615for transmission of ACK/NACKs associated with the PDCCH1 2618A and/orPDSCH1 2619A and PUCCH2 2616 for transmission of ACK/NACKs associatedwith the PDCCH2 2618B and/or PDSCH2 2619B.

A single PUCCH resource is only used for all ACK/NACK bits associatedwith the one data channel type assignment. Each PUCCH can have specificresource information. Examples of the information include specificassignment resource information (for example, a first CCE index, CORESETindex), specific semi-static PUCCH resource index and time, frequency,code, layer, and/or port resource information.

HARQ Feedback by Piggybacking UCIs

When using HARQ feedback an uplink data channel is assigned to allow theUE a channel for providing an acknowledgement or negativeacknowledgement as to whether information transmitted in the downlinkdirection was received and decoded. In some implementations according tothe present application, one common Physical Uplink Shared Channel(PUSCH) is allocated for transmission of all ACK/NACK bits, carried inan Uplink Control Information (UCI) message, that are associated withvarious DL PDCCHs. An example of this is illustrated in FIG. 26C. FIG.26C illustrates an example of a transmission resource including PDCCH12628 a being transmitted along with PDSCH1 2629A from a first TRP andPDCCH2 2628B being transmitted along with PDSCH2 2629B from a secondTRP. Also included in FIG. 26C is a single common PUSCH 2625A fortransmission of ACKs and NACKs associated with PDSCHs 2629A and 2629Bcarried inside a single common UCI 2625B.

The total number of combined ACK/NACK bits may be determined based onone or more of the following scenarios. In a first scenario, the numberof ACK/NACK bits that are transmitted by the UE is based on a number ofsemi-statically configured maximum PDCCHs. In a second scenario, thenumber of ACK/NACK bits is based on a number of semi-staticallyconfigured codewords, for example the number of codewords in a transportblock (TB). In a third scenario, the number of ACK/NACK bits is based ona number of semi-statically configured code blocks (CB) or code blockgroups (CBG). One or more CB or CBG form a codeword, as can be seen inthe example of FIG. 27 .

In another implementation, as shown in FIG. 26D, separate PUSCH(s) aretransmitted for ACK/NACK bits that are associated with differentassignments. FIG. 26D illustrates an example of a transmission resourceincluding PDCCH1 2638A being transmitted along with PDSCH1 2639A from afirst TRP and PDCCH2 2638B being transmitted along with PDSCH2 2639Bfrom a second TRP. Also included in FIG. 7D are two UCIs, UCI1 2635B fortransmission of ACKs and NACKs associated with the DL assignments foundin the PDSCH1 2639A and UCI2 2636B for transmission of ACKs and NACKsassociated with the DL assignments found in the PDSCH2 2639B.

A single PUSCH resource is only used for all ACK/NACK bits associatedwith the one data channel type assignment. Each PUSCH can have specificresource information. Examples of the information include specificassignment which can be any one or more of time, frequency, code, layer,and/or port resource information.

In another implementation, as shown in FIG. 26E, a hybrid approach canbe used whereby some ACKs and NACKs associated with a given DLassignment are transmitted over the PUCCH resources associated to thatDL assignment, while other ACKs and NACKs associated with another DLassignment are transmitted over the PUSCH resources associated with thatother DL assignment. FIG. 26E illustrates an example of a transmissionresource including PDCCH1 2648A being transmitted along with PDSCH12649A from a first TRP and PDCCH2 2648B being transmitted along withPDSCH2 2649B from a second TRP. Also included in FIG. 26E is PUCCH1 2645for transmission of ACKs and NACKs associated with the DL assignmentsfound in the PDSCH1 2649A and PUSCH2 2646A and UCI2 2646B fortransmission of ACKs and NACKs associated with the DL assignments foundin the PDSCH2 2649B.

In another implementation, as shown in FIG. 26F, a single common PUCCH2655 is used for all ACK/NACK bits associated with the PDCCHs 2658 a and2659 a that the UE received. The UE also transmits a single common PUSCH2656 which is associated with one out of all the PDCCHs but no UCI ispiggybacked on the single common PUSCH.

In another implementation, as shown in FIG. 26G, separate PUCCHs 2665Aand 2666A are used for ACK/NACK bits associated with different PDCCHs2668A and 2669A that the UE received. The UE also transmits separatePUSCHs 2665B and 2666B where each PUSCH is associated with one out ofall the PDCCHs but no UCIs are piggybacked on the separate PUSCHs.

Association Between UL and Assignment

In some embodiments, the network provides the UE with an associationbetween UL power control parameters and a reference PDCCH of multiplePDCCHs that can be used for scheduling PDSCH and which contain dynamictransmission power control or transmission power command (TPC). Theassociation may be provided using RRC signaling. In a first example inwhich there are two PDCCH (PDCCH1 and PDCCH2), a UE is configured to useTPC from PDCCH1 or PDCCH2 for the dynamic adjustment for PUSCH and/orPUCCH power control, in this example, PDCCH1 or PDCCH2 can be areference PDCCH for TPC operation. In a second example in which thereare two PDCCH (PDCCH1 and PDCCH2), one PDCCH is associated with thespecific PUSCH and/or PUCCH, then this PDCCH will be regarded as adefault reference PDCCH for the specific PUSCH and/or PUCCH TPCoperation. In a third example, for multiple PUSCHs and/or PUCCHs whichare associated different PDCCHs, the specific and/or common open-looppower control parameter can be configured. In this example, specificopen-loop power control parameter can be at least one of first nominalpower, second UE-specific power, pathloss compensation factor and commonopen-loop power control parameter can be at least one of first nominalpower, second UE-specific power, pathloss compensation factor.

A representative example of this is shown in FIG. 28A. FIG. 28Aillustrates a first PDCCH1 2802 and a second PDCCH2 2804 which are bothfor scheduling PDSCH and contains dynamic TPC. The two PDCCH 2802 and2804 may be channels in a transmission source shared by two TRPs. FIG.28A also includes a PUSCH 2808. The PDCCH can include TPC informationfor use by the UE when transmitting in the uplink direction. The networkmay provide an association to the UE that TPC information that is partof a PDCCH1 2802 should be used for uplink power control (UL PC) for aphysical uplink shared channel (PUSCH). As shown in FIG. 24A, a TRP mayschedule PUSCH, PDSCH, or both, for a given UE. With relation to FIG.28A, the TRP associated with PDCCH2 2804 may not schedule a PUSCH forthe UE and thus the UE should not use TPC information that istransmitted by the TRP associated with PDCCH2 2804

In some embodiments, the UE is provided with an association between anuplink sounding resource signal (UL SRS) triggering parameter and areference PDCCH of multiple PDCCHs that can be used for carrying SRStriggering parameter. The association may be provided using RRCsignaling. In a first example in which there are two PDCCH (PDCCH1 andPDCCH2) and each PDCCH has one SRS trigger, a UE is configured to useSRS trigger from PDCCH1 or PDCCH2 for SRS transmission, in this example,PDCCH1 or PDCCH2 can be a reference PDCCH for TPC operation. Arepresentative example of this is shown in FIG. 28B. FIG. 28Billustrates a first PDCCH1 2812 and a second PDCCH2 2814. FIG. 28B alsoincludes a SRS transmission 2818. The PDCCH 2812 and 2814 may include aSRS triggering parameter respectively. The network may provide anassociation to the UE that and the SRS triggering parameter that is partof a PDCCH12812 should be used for SRS transmission. Defining andutilizing such an association may help the UE avoid errors to using anincorrect SRS trigger.

Association Between UL and Assignment

In some embodiments, the UE is provided with an association betweenseparate uplink sounding resource signal (UL SRS) triggering parametersand the assignment identity. The association may be provided using RRCsignaling. A representative example of this is shown in FIG. 28C. FIG.28C illustrates a first PDCCH1 2822 and a second PDCCH2 2824. FIG. 28Calso includes SRS1 2828 associated to PDCCH1 2822 and SRS2 2829associated to PDCCH2 2824. The PDCCH 2822 and 2824 may include a SRStriggering parameter. The network may provide an association to the UEthat the SRS triggering parameter that is part of PDCCH1 2822 should beused for SRS transmission SRS1 2828 and the SRS triggering parameterthat is part of PDCCH2 2824 should be used for SRS transmission SRS22829. Defining and utilizing such an association may help the UE avoiderrors to using incorrect SRS triggers. The network may provide theseparate UL SRS triggers a set of configuration parameters such that theUE services the separate SRS triggers using different time resource,frequency resource, code resource, layer resource, port resource, periodinformation and bandwidth information.

In some embodiments, the network may define any further higher-layersignaling parameters using long-term coordination rules used to ensurethat different TRPs do not send UL SRS triggers using the same set ofconfiguration parameters. The network may also provide separate UL SRStriggers the exact same set of configuration parameters, in which casethe UE treats them as one and the same request.

HARQ Process Association

In some implementations, one UE can be configured with a differentmaximum HARQ process number for PUSCH or PDSCH according to theconfigured number of PDCCH for one channel type (unicast or UE-specific)and the same C-RNTI type and one cell or component carrier. The maximumHARQ process number for PUSCH and PDSCH is two separate definitions. Ina first example, the UE is configured with a first maximum HARQ processnumber associated with first PDCCH number for PDSCH or PUSCH that isconfigured to be monitored simultaneously and the UE is configured witha second maximum HARQ process number for second PDCCH number for PDSCHor PUSCH that is configured to be monitored simultaneously. In thisexample, first and/or second maximum HARQ process number is configuredwith RRC signaling. In a second example, the UE is configured to derivethe maximum HARQ process number based on the number of PDCCH and the onemaximum HARQ process number which is defined for one PDSCH or PUSCH. Inthis example UE is configured with one maximum HARQ process number Nmaxfor one PDCCH for PDSCH or PUSCH and derive another maximum HARQ processnumber by Nmax*N wherein N is another configured number of PDCCH forPDSCH or PUSCH.

In some implementations, a HARQ process ID (HPID) associated with aspecific assignment can be derived from parameters known to the UE. Forexample, the UE can use an initial HARQ process ID (HPIDIni) carried bythe assignment, an assignment identity (AI) associated with theassignment and a maximum number of HARQ processes per assignment (Nmax).In such a scenario, the HPID can then be determined using therelationship of HPID=HPIDIni+AI×Nmax.

In a particular example scenario for a single TRP (i.e. one PDCCH) in acell there are eight possible HARQ processes, i.e. 0 to 7, defined usingthree bits. This can be seen in FIG. 29A, i.e. HP1 to HPN, where N=8.For a scenario having two TRPs (i.e. two PDCCHs) in the cell, each TRP(associated with specific PDCCH) may have eight respective HARQprocesses, each defined by three bits. If each TRP has a uniqueassignment identity value within the cell then the assignment identitycan be combined with the HARQ process numbers for each respective TRP toavoid confusion between HARQ processes. In the case of two TRPs,utilizing a single additional bit can be used as the assignmentidentity, i.e. a “0” bit for assignments from a first TRP and a “1” bitassignments for the second TRP. The assignment identity is known by theUE, either explicitly or implicitly, as described above, and enables theHARQ process to be determined for assignments from the respective TRPs.This can be seen in FIG. 29A, i.e. HP1 to HP2×N, where N=8.

While the above example describes the use of three bits for a total ofeight values of HP, it is to be understood that this is merely anexample and in some implementation 2 bits for four HP or more than threebits could be used. In addition, as the second example described asituation with two TRP, each having an associated assignment identitythat could be identified with a single value of one bit, it should beunderstood that for a large number of TRP, the assignment identity maybe two or more bits.

In some embodiments, when multiple TRPs are being used in the sameregion, or in adjacent regions, in for example the case of handoff,there are various joint transmission options that can be utilized forcommunicating with UEs. As discussed above, in one option, informationcan be transmitted using a single PDCCH from one TRP and information canbe transmitted using a same PDSCH from one or multiple TRPs orinformation can be transmitted on different layers of a same PDSCH frommore than one TRP. In another option, information can be transmittedusing a single PDCCH that schedules information on different PDSCHstransmitted from more than one respective TRP. In a further option,multiple and independent PDCCHs can be transmitted that scheduleinformation on different PDSCHs transmitted from more than onerespective TRP.

Scheduling by multiple TRPs can be either coordinated ornon-coordinated. The TRPs can schedule transmission using the same ordifferent physical layer (PHY) resources. As mentioned above, PDCCHsfrom more than one TRP can map to same or different CORESETs or CORESETgroup and data channels or PDSCHs of the respective PDCCHs may beassigned orthogonal resources or overlapping resources.

In some implementations, the TRPs may perform joint pre-emption of partof resources assigned a traffic/service type to provide enhancedreliability to a transmission of another traffic/service type. Inparticular, transmission can be scheduled for multiple traffic typesand/or services in a shared time-frequency region. One traffic type suchas Ultra Reliable Low Latency Communications (URLLC) may require morereliability and faster transmission opportunity than other traffic typesuch as enhanced Mobile Broadband (eMBB). Joint pre-emption by multipleTRPs may benefit at least the cell-edge URLLC UEs. For example, aserving TRP, or a network controller controlling a serving TRP and a TRPin an adjacent region in a same or a different cell, may cause a portionof a transmission resource utilized by the TRP in the adjacent region tobe punctured and thus not transmit during a time when the serving TRP istransmitting to URLLC UE to avoid potential interference at the URLLC UEbetween transmissions from the serving TRP and the TRP in the adjacentregion.

Some implementation of the present application may exploit cooperationof multiple TRPs to further to enhance reliability of PDCCH and PDSCH,or both. Particular examples of techniques that could be used are usingshared transmission or data duplication from TRPs, within the limits ofbackhaul latency constraints, using coded transmissions from multipleTRPs, and soft handover and data duplication via reserved/configuredresources.

For cooperation between TRPs, scheduling can occur either centrally orindependently. FIG. 30A illustrates an example of central scheduling inwhich a central scheduler 3001 communicates scheduling information andUE data to both a Primary TRP (P-TRP) 3005 and a Secondary TRP (S-TRP)3007. The P-TRP 3005 and the S-TRP 3007 then share transmission. TheS-TRP can transmit a separately encoded version of the same transmissionblock (TB). The particular example shown in FIG. 30A is shown to be anAlamouti-type shared transmission, which when received by UE 3008provides all the relevant information to the UE 3008 for decoding basedon packets received from TRPs. FIG. 30B illustrates an example ofindependent scheduling in which there are different HARQ entities fromeach of P-TRP 3015 and the S-TRP 3017. There is no PHY layer combiningas can be achieved in FIG. 30A, because the radio link control (RLC)packet segmentation is different at the TRPs.

Note that the TRPs are mentioned in the application in a generalcontext. TRPs can belong to a same or different TRP group, where TRPgroups may belong to a same or different cell. A P-TRP or S-TRP asdiscussed below may refer to single TRP or a TRP group.

Generally, when referring to multiple PDCCH(s) in the following, it isto be understood that this at least corresponds to multiple differentPDCCH(s) associated with at least one UE-specific data channel, for DLand UL, with a same or different RNTI type.

For soft-handover between TRPs, either within a region/cell or betweenadjacent regions/cells, a resource set comprising a time-frequencyresource can be configured for a UE and activated for the UE for thepurpose of dual connectivity (DC), i.e. a UE connecting to at least twoTRPs and receiving/transmitting over multiple links. In someembodiments, the configured resources can be assigned in asemi-persistent scheduling (SPS) manner. A new PDCCH may not be requiredfor using the configured resources that contain data duplication. As aresult, the UE may save battery power by not having to monitor foradditional PDCCH during DC.

The configured resource can be different from the scheduled resourcesfrom the P-TRP.

The resource set is activated before the handover begins. An activationsignal notifies the UE when to expect a transmission over the configuredresources from an S-TRP. The activation signal may also notify starttime and duration of the configured resource set. The activation signalcan be provided to the UE by any one of or a combination of thefollowing types of signaling: a UE specific DCI or a group DCI; RRCsignaling; or Media Access Control Control Element (MAC CE) signaling. Ade-activation signal can be provided to the UE by any one of or acombination of the following types of signaling: a UE specific DCI or agroup DCI; RRC signaling; or Media Access Control Control Element (MACCE) signaling.

The UE receives transmission from multiple links. The data transmissionfrom multiple TRPs can be based on same information bits or same TB. Oneapplication of this scheme is data duplication during the handoverprocess. At least one TRP provides dynamically scheduled transmissionvia PDCCH and optionally, at least one TRP transmits over one or moreconfigured resources. In one example, transmission over the configuredresource set can be performed using semi-persistent signaling as opposedto using a dynamic PDCCH transmission. Here in the context ofsemi-persistent scheduling, it is assumed that a resource set isconfigured and an activation signal is provided before using theresource set for transmission. The de-activation signal may follow whichinstructs the UE not to receive or transmit further in the configuredresource. Data duplication may be used over the configured resource set,possibly in conjunction with scheduled transmission from at least one ofthe TRPs. Data duplication during the handover phase can increase URLLCreliability.

Data duplication can be performed in different ways. For example theduplication may be performed using different variations of protocolstacks; duplication at PDCP layer, at the RLC layer or at the MAC layer.Duplication can also be shared via backhaul from the P-TRP to the S-TRPvia the X2 or Xn interface.

Both inter-frequency handover, changing from one frequency to anotherduring handover, and intra-frequency handover, maintaining the samefrequency during handover, are contemplated for DC.

Resources can be configured for use for transmission from differentcells at different times during the handover process. When activated,the configured resource allows RRC configuration or re-configuration, orboth, between the serving cell and the target cell. The use of theconfigured resources can be transparent to the UE, i.e., different TRPcan use the configured resource for transmission to the UE at differenttime occasions during the handover phase.

FIG. 31A illustrates an example of two adjacent cells 3102 and 3104,each having a TRP, 3107 and 3109, respectively. A UE 3112 is located atthe overlap of the two cells 3102 and 3104 and is being handed overbetween TRP 3107 and TRP 3109. FIG. 31B illustrates several sequentialresource blocks in the time domain. As TRP 3107 is initially the servingTRP, a first resource block 3120 includes PDCCH and scheduledtransmission sent by TRP 3107. Third and fourth resource blocks occurduring the handover. The third resource block 3130 includes PDCCH andscheduled transmission sent by the TRP 3107 as it is still the servingcell. The third resource block 3130 also includes a configured resourcefor information to be sent by TRP 3109. Optionally, the configuredresources may allow TRP 3109 to be established as the serving cell. Bythe time the fourth resource block 3140 occurs, TRP 3109 has become theserving cell, and so the fourth resource block 3140 includes control andscheduled transmission sent by the TRP 3109. The fourth resource block3140 also includes a configured resource for information to be sent byTRP 3107. By the time the sixth resource 3150 block occurs, TRP 3109sends control and scheduled transmission.

Transmission over the configured resource set is received by the UE in aTRP-transparent manner, i.e. the UE may not know from which TRP thetransmission is from. In some embodiments, Quasi-Co-Location (QCL)information may be provided to the UE, if the QCL information isdifferent for the two TRPs.

In some implementations, S-TRP may puncture ongoing transmissions overthe configured resource for URLLC UEs to avoid interference and improvereliability. The configured resource set for URLLC UEs that are notactivated can be used for other transmission.

Activation and/or deactivation signal can be communicated by any TRPthat is associated with the UE. In one example, TRP 3107 providesactivation signal and TRP 3109 provides deactivation signal.

In some scenarios there may not be a configured or reserved resource. Insuch a case the S-TRP may dynamically schedule duplication of theinformation in a time-frequency resource. The UE may receive scheduledtransmission over multiple links where one or more links are used forscheduling data duplication. In such a scenario, the UE needs to bepreviously configured to monitor multiple search spaces for thepossibility of the duplicate information that is dynamically scheduledby the S-TRP. The P-TRP and S-TRP may transmit control information in asame or different CORESETs for scheduling duplicate transmissions.

It is to be understood that DC is mentioned as an example of when aconfigured resource set can be used for data duplication. Moregenerally, the structure of a configured resource set, which is usedbased on activation/de-activation signaling, can be used in otherscenarios, for example, in an interference limited scenario.

In another embodiment, the dynamically scheduled transmission andtransmission over configured resource can be performed by a same TRP orTRP group.

In one example, there may or may not be any PUCCH or uplink channelinformation (UCI) resource, or both, associated with the DL transmissionover the configured resource set. If both serving and target cells aretransmitting a same TB or different versions of the same TB, then the UEcan combine the scheduled transmission and transmission over theconfigured resource set. HARQ feedback can be sent in the PUCCH resourceconfigured for the UE or indicated by the scheduling informationreceived, or both. In another example, there may be a PUCCH and/or UCIresource semi-statically associated with the configured resource set. Inthat case, the UE sends two HARQ feedbacks, one for the scheduledtransmission and another for the transmission that occurred over theconfigured resource set. If data is duplicated based on one MAC, i.e., asame or versions of a same TB that is scheduled from a serving cell andthat is transmitted over the configured resource set, then a same HARQfeedback can be duplicated in the two associated PUCCH resources. Ifdata is duplicated at a higher layer, for example, PDCP, then the UE maynot identify the TBs transmitted over the two links as based on the sameinformation bits at the PHY layer. In that case, HARQ feedback would beindependent.

In some implementations, a single PDCCH is transmitted from the P-TRPand data transmissions (PDSCH) occur from the P-TRP and one or moreS-TRP. Different repetition groups are transmitted from different TRPs.The P-TRP is responsible for scheduling up to X repetitions, where Krepetitions are transmitted by the P-TRP, K<X, and where K and X areinteger values. This leaves K-X repetitions to be transmitted by the oneor more S-TRPs. The variable K is configurable and may for example bebased on inter-TRP backhaul delay. Not all of the X repetitions may benecessary for a given transmission, for example if the initialtransmission or any of the retransmissions are acknowledged as receivedand thus the S-TRP may not be required to transmit. The extent ofsharing the transmission can depend on backhaul latency between theTRPs.

FIG. 32A illustrates an example of centralized scheduling in which acentral scheduler 3201 communicates scheduling information to both P-TRP3205 and S-TRP 3207. The initial transmission and the one or moreretransmission can be sent from different TRPs. In FIG. 32A, P-TRP 3205transmits repetitions R1 to R4 and S-TRP 3207 transmits repetitions R5and R6. The sequence of repetitions shown in FIG. 32A is only anexample. In general, multiple TRP groups can participate in transmissionof a TB where at least one TRP group (for example, P-TRP in FIG. 32A)can schedule one or a combination of initial transmission andrepetitions and subsequent transmission or re-transmissions. Optionally,another TRP group (for example, S-TRP in FIG. 32A) transmits one or acombination of initial transmission and repetitions and subsequenttransmission or re-transmissions of the same TB and the transmission canbe either scheduled by a same TRP group or a different TRP group (forexample, P-TRP in FIG. 32A) or by a centralized scheduler. A TRP groupconsists of at least one TRP. One TRP can exclusively belong to one TRPgroup or may belong to multiple groups. In one example, a P-TRPschedules at least an initial transmission and an S-TRP schedules atleast one re-transmission of a same TB. Alternatively, the P-TRPschedules an initial transmission and one set of re-transmissions andthe S-TRP schedules another set of re-transmissions of the same TB.

FIG. 32B illustrates an example of scheduling in which P-TRP 3215 isresponsible for scheduling repetitions by P-TRP 3215 and S-TRP 3217. Inthis case there is a backhaul connection between P-TRP 3205 and S-TRP3207. The S-TRP 3207 receives scheduling information from P-TRP 3205. InFIG. 32B, P-TRP 3205 transmits repetitions R1 to R4 and S-TRP 3207 isscheduled by P-TRP 3205 to transmit repetitions R5 and R6. Here, S-TRPis assumed to obtain at least scheduling information over the backhaulfrom P-TRP within the latency constraint of the service type. The S-TRPmay have data already available or optionally may receive data over thebackhaul from P-TRP.

Quasi-Co-Location (QCL) information pertaining to the TRPs may or maynot be signaled to the UE. The signaling can be in a Downlink ControlIndicator (DCI) for use by the UE. Alternatively, signaling can besemi-static or implicitly derived from other communication property forexample RS.

In some scenarios, the S-TRP may update scheduling for remainingre-transmissions.

In some embodiments, when independent PDCCHs are transmitted frommultiple TRPs, part of the data may be independently scheduled from theS-TRP. The PDCCH may be transmitted using multiple repetitions. TheP-TRP shares scheduling information and/or data with the S-TRP. Uponreceiving the scheduling information, the S-TRP can schedulere-transmissions of the packet independently or in coordination with theP-TRP.

In some implementations, the S-TRP can repeat the same PDCCH that wassent by P-TRP for initial transmission. The UE may or may not be able todetect PDCCH from the first transmission. Repeating the PDCCH mayincrease reliability of transmission.

The transmissions from the P-TRP and the S-TRP can be coordinated oruncoordinated.

FIG. 33 illustrates an example of several sequential resource blocks. Inthe first resource block the P-TRP schedules an initial transmission. Aninter-TRP backhaul delay in this particular example is substantially theequivalent to the duration of four resource blocks. The P-TRP canschedule a retransmission upon receiving a NACK. The S-TRP alsoschedules a retransmission upon receiving the scheduling information ordata, or both. The S-TRP may or may not be aware of subsequent P-TRPscheduled retransmissions. The timing for an ACK/NACK set by P-TRPduring the first transmission can be before or after the scheduledtransmission from the S-TRP.

In one example, the S-TRP may update ACK/NACK timing set by P-TRP if theS-TRP is scheduling (re)-transmission of a same TB. The UE can beconfigured to monitor one or multiple search spaces where controlinformation from the P-TRP and the S-TRP are transmitted.

In some embodiments, data duplication can be performed using the PacketData Conversion Protocol (PDCP) function. The duplicate packets arereceived by multiple access nodes over an interface between a P-TRP andan S-TRP (Xn interface) and forwarded to the UE. The UE detects thepacket duplication and forwards a single packet to the upper layers.Ideal backhaul provides communication between TRPs that is within thelatency requirement.

The UE is configured to monitor one or multiple CORESETs. The UE may notneed to know which CORESET is being used by which TRP. It is possiblethat multiple TRPs can use the same CORESET for PDCCH repetition. Thesame PDCCH can be received from multiple TRPs over the same or differentCORESETs. PDCCHs may refer to the same or different PHY resources forPDSCH transmission. A number of PDCCH repetitions can be configured orindicated in the first PDCCH sent. DCI fields can be used for schedulingPDCCH repetitions. Scheduling independent PDCCHs from different TRPs maycorrespond to same HARQ processes. In this case, two TRPs share a sameHARQ entity without restriction, i.e., both can schedule a same HARQprocess ID.

Alternatively, one HARQ entity is shared among the TRPs and one TRPtransmits a set of HARQ process which is different from the set of HARQprocesses scheduled by other TRP.

Some embodiments of the present application provide mechanisms to avoidPUCCH resource allocation conflicts when independent PDCCHs areassigned. If a PUCCH resource is indicated in a DCI, ACKs and NACKs,resulting from HARQ processes scheduled by different TRPs may or may notmap to a same PUCCH resource. In some embodiments, pre-configured rulescan be applied to aid in avoiding conflicts. The PDCCHs may betransmitted in different CORESETs and an association of a PDCCH to aCORESET location can be exploited to multiplex HARQ feedbacks of twoPDCCHs in a common PUCCH resource. The two feedbacks may be concatenatedor code-multiplexed with each other. A sequence of concatenation or oneor more codes used for multiplexing can be associated with one or moreof a CORESET location, a given DMRS configuration, other property ofPDCCH, or communication link, so that TRPs can distinguish the HARQfeedback received in the same PUCCH resource. If the PDCCHs indicatethat the same data or HARQ process is being transmitted by multipleTRPs, then the UE can combine the transmissions received and send HARQfeedback in the PUCCH resource that is received by both TRPs. Two TRPsare used as example described above. However, it is to be understoodthat the solution can be extended to an arbitrary number of TRPs.

In some embodiments, if different PUCCH resources are indicated for asame HARQ process by different PDCCHs, those PUCCHs can be used forPUCCH repetition, i.e., a same feedback repeated over multiple PUCCHresources. In some embodiments, the UE is configured to use oneindicated PUCCH resource For example, one PDCCH indicates a PUCCHresource whereas other PDCCH does not indicate any PUCCH resource.Alternatively, none of the PDCCHs indicate a PUCCH resource and the UEtransmits a PUCCH over the pre-configured resource. The two PDCCHsschedule same or different versions of same TB or HARQ process.

In one embodiment, the UE combines the transmissions received and sendsHARQ feedback in the indicated or configured PUCCH/UCI resources.

In one embodiment, the two PDCCHs scheduling transmission of a same HARQprocess can be received at different times and the PDCCH that isreceived later can update HARQ timing information. The UE can beconfigured so that if the second or repeated PDCCH arrives before aspecified interval, the UE can follow the updated timing. Alternatively,feedback is repeated in both indicated PUCCH resources as one TRP maynot be aware of the HARQ timing and/or PUCCH resource indicated by theother TRP.

In some implementations, the PDCCH may indicate n units of resources forn repetitions of the PUCCH. In some embodiments, for URLLC UEs inparticular, the UEs may be configured with a PUCCH repetition number.

Based on indicated PUCCH resource(s), the configuration of the PUCCH mayfollow a hopping pattern for n repetitions.

The repetition number can be dynamically indicated in a field in thePDCCH. The UE may follow a pre-configured hopping pattern forrepetition. Each repetition occasion may comprise a symbol group, whichcan be a minimum of one symbol. The repetitions may or may not becontiguous.

In one embodiment, the UE may be provided a PUCCH resource together withrepetition number. Both PUCCH resource and repetition number can beindicated in a DCI. Alternatively, the PUCCH resource and the repetitionnumber are configured by a higher layer. In another example, the PUCCHresource is indicated in a DCI from the set of PUCCH resourceconfigurations supported by a UE and a repetition number is configuredby a higher layer. Starting from the indicated PUCCH resource, the UEcan apply a pre-configured hopping rule for repeating PUCCH or HARQfeedback in subsequent symbols. Alternatively, the UE may supportmultiple configured hopping patterns and one of the hopping patterns isindicated to the UE in the DCI.

In some embodiments, the PDCCHs that can potentially map to a sameCORESET can be associated with different DMRS configurations. Each DMRSconfiguration can be associated with a QCL.

In some embodiments, some CORESETs are associated with particular TRPsso that PDCCHs do not necessarily need have different DMRSconfigurations.

In some scenarios, PDCCH repetitions can be utilized to enhancereliability. The PDCCH can be repeated in the time domain. The PDCCH canbe repeated in consecutive monitoring occasions or data repetitionoccasions. The PDCCH can also be repeated in the frequency domain. If aUE is configured with multiple CORESET candidates, PDCCH can be repeatedover multiple CORESETs in time and/or frequency. The TRP stops PDCCHrepetitions once an ACK is received or after a pre-configured number ofrepetitions.

Using multiple CORESETs for PDCCH repetition can be costly. In somecases a PDCCH may be properly received and decoded by the UE, but theTRP may not receive any indication that the PDCCH has been successfullyreceived. As a set number of repetitions may be performed by the TRP,multiple PDCCH repetitions occur that are not needed. Some of the PDCCHrepetitions could be avoided had the TRP received a notification. FIG.34A illustrates an example of three time-frequency resource blocks 3402,3404, 3406, in which each resource block begins with a NR-PDCCH thatidentifies an assignment in a shared resource for a UE subsequent to thePDCCH. In the first and second transmission blocks 3402 and 3404 theNR-PDCCH is not successfully received by the UE. The NR-PDCCH issuccessfully received in the third transmission block 3406. FIG. 34Bshows another example of several PDCCH 3412 and 3414 that are sent butnot successfully detected by the UE at a first and a second monitoringoccasion and one PDCCH 3416 that is eventually successfully detected bythe UE at a second instance of the second monitoring occasion.Furthermore, if CORESETs of different UEs are configured in anoverlapping manner, excessive PDCCH repetition may block scheduling ofother services. Some embodiments of the application may aid in reducingPDCCH repetition while at the same time ensuring PDCCH is received bythe UE.

Some implementations of the present application involve supporting thereduction of overhead for signaling that may not be needed. For example,a PDCCH may be transmitted multiple times to ensure the PDCCH isreceived by the UE. However, if the UE can transmit some form ofacknowledgement that the PDCCH has been received, then the PDCCH may notneed to be re-transmitted multiple times. As a result, the resourcesused for the PDCCH retransmission could be used for something else. Someembodiments of the application include a UL channel being configured tosend PDCCH acknowledgement (PDCCH-ACK). The PDCCH-ACK can be used by theTRP as in indication to stop PDCCH repetitions. The PDCCH-ACK could bemultiplexed with uplink signaling such as PUCCH and scheduling request(SR). The PDCCH-ACK may be signaled using grant based or grant freesignaling.

In some embodiments, UEs can be configured with UL channel resources tosend an acknowledgement if the PDCCH is detected (PDCCH-ACK). ThePDCCH-ACK timing can be earlier than the timing configured for dataACK/NACKs.

A resource can be allocated in the UL channel x μs after each PDCCHmonitoring or repetition occasion to allow the UE to send anacknowledgement if the UE successfully detects the PDCCH. The value of xcan be a function of UE capability. In some embodiments, the UE may senda negative acknowledgement if the UE does not successfully detect thePDCCH. If the TRP does not receive the PDCCH-ACK or a NACK, then the TRPwould continue to send repetitions of the PDCCH up to a predefinednumber.

The resources used for the PDCCH-ACK may span a single or multiplesymbols in the UL channel.

FIG. 35 illustrates a representation of DL and UL signaling. In the DL3502, a channel of the transmission resource 3504 is allocated forPDCCHs and the associated data assignments for the PDCCHs. In the UL3512, a channel of the transmission resource is allocated for PDCCH-ACKS3514 and data ACK/NACKs 3516. The relationships between the PDCCH andPDCCH-ACKs and the PDCCHs and the ACK/NACKS are indicated at 3522 and3524, respectively. As can be seen, the PDCCH-ACK for a particular PDCCHis prior to the data ACK-NACK for the same PDCCH.

The PDCCH-ACK may simply be a single bit to indicate a successfullydetected PDCCH.

Channel design options may include a configured one or more resource ina PUCCH region. In some embodiments, PDCCH-ACKs can be multiplexed withone another. A separate resource is configured or indicated for sendingPDCCH-ACKs. In some embodiments, PDCCH-ACKs can be multiplexed with dataACK/NACKs or sent in the resources configured or indicated for dataACK/NACK transmission. When the PDCCH-ACKs are multiplexed with dataACK/NACKs or sent in the same resource indicated for data ACK/NACK,based on configured data ACK/NACK timing indicated in a DCI, the TRP canidentify what is a PDCCH-ACK and what is a data ACK/NACK.

In some embodiments, the channel design for sending PDCCH-ACK may bereserved resources similar to that used for a scheduling request (SR).

In some embodiments, the channel design may involve combining thePDCCH-ACK with SR if more than one bit is used for SR. For example, whentwo bits are used for SR, the value “11” indicates a PDCCH-ACK, while“00”, “01” and “01” are specific to SR.

In some embodiments, the PDCCH-ACK can be sent using grant-free (GF)transmission. PDCCH-ACKs of multiple UEs may overlap, but could beidentified by embedded reference signals (RS) or in code-domain.

It can be understood that the reliability of such a PDCCH-ACK channel isnot as stringent as a data ACK/NACK channel. While a PDCCH-ACK may bebeneficial to reducing overhead for example, it is not as critical asACK/NACKs for data.

A UE may receive both enhanced mobile broadcast (eMBB) and URLLC trafficusing same DCI format. The UE may have different higher layerconfigurations for eMBB and URLLC traffic. Identification of whichtraffic is scheduled is important to avoid errors in detection. Radioresource control (RRC) configuration can be different for the differenttypes of traffic. One solution is to associate the UE with differentC-RNTIs for eMBB traffic and URLLC traffic. Or in general, a UE may beassociated with multiple C-RNTIs, where each C-RNTI may correspond to aservice type. The UE may obtain the C-RNTI along with a RRCconfiguration for each traffic type supported or may receive the C-RNTIsindependently from the RRC configuration, for example, during initialaccess or a different RRC configuration.

Some embodiments of the application provide higher detection reliabilityof the PDCCH. As initial transmission of the PDCCH may not besuccessfully detected by the UE, re-transmission of PDCCH should includetransmit block size (TBS) information.

In the case of LTE for example, re-transmissions do not receive TBSinformation in the DCI. Such LTE re-transmissions provide modulation andresource block allocation information and assume that TBS information isreceived in an initial transmission DCI. In particular for the case ofURLLC, a failure to detect the initial transmission DCI can bedetrimental in terms of performance if the TBS information is onlytransmitted in the initial transmission DCI. Re-transmission/repetitioncan occur before ACK/NACK for data. Hence, the TRP may not be aware ofwhether the UE has successfully received the first PDCCH sent. The UEcan be configured to identify TBS in each of the repeated PDCCH or atleast for the PDCCH repetitions that occur before the ACK/NACK timingset by the first PDCCH sent.

In one embodiment, PDCCH or assignment can be repeated in time and/orfrequency domain. In one example, repeated PDCCHs are sent inoverlapping or non-overlapping frequency resources, i.e., the searchspaces where the PDCCHs are transmitted can be overlapping ornon-overlapping. The repeated PDCCHs in frequency may correspond to acommon HARQ process or a TB transmission however MCS and/or resourceassignment can be same or different. Repeated PDCCHs can be transmittedin same CORESET or different CORESETs. Repeated PDCCHs may have same ordifferent DMRS configurations and/or same or different QCL association.In another example, PDCCH can be repeated in time. For each repetitionoccasion, same or different CORESET can be used for PDCCH repetition.The PDCCH repetition number can be configured or dynamically indicated.The PDCCH repetition occasion can be every x symbols, where x can be assmall as one symbol. In one example, PDCCH is repeated in consecutivemonitoring occasions. In another example, PDCCH repetition occasions maycomprise non-consecutive PDCCH monitoring occasions. In another example,the PDCCH repetition occasion may not align with PDCCH monitoringoccasions. If a UE detects multiple PDCCHs that correspond totransmission of same TB, UE can combine them for robustness or discardthe subsequent or other PDCCH repetitions after it detects at least onePDCCH.

A first option to improve PDCCH detection reliability includes a PDCCHthat schedules (re)-transmission or subsequent transmission alsoprovides TBS information again before data ACK/NACK is scheduled. Insome embodiments, the PDCCH of re-transmission can include the samemodulation coding scheme (MCS) or different MCS with the same or adifferent set of RBs compared to initial transmission. However the TBSinformation is the same. In some embodiments, different combination ofMCS and RBs can be formed from a TBS-lookup table. Hence, the PDCCHsthat are repeated can be considered self-contained in terms ofcontaining TBS information.

A second option to improve PDCCH detection reliability may includesending the initial transmission of the PDCCH in a more robust manner.For example, first PDCCH transmission can be transmitted with one ormore of: a lower code rate; a higher aggregation level; a highertransmit diversity; and a longer cyclic redundancy check (CRC) thansubsequent repetitions of PDCCH or PDCCHs that schedule re-transmission.

In some embodiments, PDCCH scheduling initial transmission may comprisea higher aggregation level than that which would be used for a(re)-transmission PDCCH. In some embodiments, the UE may receive one ormultiple PDCCHs scheduling the initial transmission, thereforerepetition occurs before the HARQ timeline that is indicated in thefirst PDCCH sent. In one embodiment, PDCCH repetition is only conductedfor initial transmission and not for (re)-transmission. In anotherembodiment, PDCCH repetition is only conducted for a group of(re)-transmissions. In another embodiment, PDCCH repetition is conductedfor initial transmission and a select group of (re)-transmission.(Re)-transmission refers to a re-transmission scheduled either before orafter HARQ feedback is received.

The self-contained PDCCH repetition typically occurs before ACK/NACKsignaling for data. Each PDCCH provides transmission block size (TBS)information. FIG. 36 illustrates a representative example of DL 3602 andUL 3604 signaling. For each PDCCH monitoring occasion a PDCCH istransmitted that includes the TBS information. The PDCCH repetitionsoccur before the HARQ for a given packet. A first PDCCH 3612 in the DL3602 is not detected by the UE as indicated by the dashed line 3616between the first PDCCH 3612 and the first proposed location 3622intended for an ACK/NACK in UL 3604. As the first PDCCH 3612 is notdetected, the UE is unaware of the proposed location 3622 for the firstACK/NACK. A first repetition of the PDCCH 3614 may or may notreconfigure the HARQ timing. In the case where the HARQ timing isreconfigured, the first repetition PDCCH 1714 maintains the originalproposed ACK/NACK location 3622. In the case where the HARQ timing ismaintained, the first repetition PDCCH 3614 maintains the originalspacing between the repeated PDCCH 3614 and a first ACK/NACK so that thefirst ACK/NACK is the second proposed ACK/NACK 3624 in the UL 3604.

For a PDCCH transmission, TBS information and the resource assignmentcan be provided. In some existing protocols, MCS information and theresource assignment can be used to provide the TBS information which theUE obtains from a look-up table. In one example, TBS information can beobtained from indicated MCS and/or RB allocation (i.e., sub-carriergroups) and/or data duration (i.e., number of symbols and/or slotsscheduled) and/or number of transmission layers and/or codebooksignature used for non-orthogonal access. MCS and/or RB allocationand/or data duration can be semi-statically indicated or dynamicallyindicated in the PDCCH. The number of resource elements (REs) occupiedby a transmission is given by the RB allocation (more generally,sub-carrier group allocation) and data duration. A configurable MCSfield can be used, which contains M bits in the PDCCH. The MCS fieldconfiguration can be UE specific or cell specific. Data durationindication can be UE specific as well. For example, for one UE theminimum duration is a symbol, whereas for another UE it can be a slot. Alook-up table approach for identifying TBS can be obtained as follows: AMCS table, either UE specific or cell specific, is formed where acombination of bits in MCS field correspond to an identifier1,identifier1 maps to another identifier2 based on data durationindicated, which can be UE specific, in another Table (optional),identifier2 maps to a TBS for a given number of RBs allocated in anotherTable. Each of these Tables can be configured in a UE specific manner.For example, 00 in a MCS field containing 2 bits may map to differentvalues of Modulation and coding for different UEs. Similarly, 10 in adata duration indication field may indicate 3 symbols duration for oneUE whereas it means 3 slots for another UE. Hence, the exact valueindicated by MCS and data duration field can be UE specific andcorrespondingly, the identifiers mentioned above, if UE specific, couldmap to different TBS for a given number of RBs or sub-carrier groupallocated. Hence, contents of the Tables can be UE specific which everyUE is configured with. In another example, TBS indication can be servicespecific, i.e., eMBB and URLLC may adopt different mapping mechanism.

In the case of URLLC there may only be a few options for providing theTBS information. A first signaling option includes explicitly providingthe TBS information in a TBS specific field for example if only a selectMCS is used. A second signaling option includes signaling the modulationtype and the resource assignment. Alternatively, TBS information (theindication maps to a MCS and number of RBs) is explicitly provided inthe DCI and a starting RB index is provided if consecutive RB allocationis used. From the TBS information, the UE identifies how many RBs aregoing to be used. In another example, only TBS is provided in anexplicit field of n bits. Each combination of bits refers to a certainMCS and RB assignment. In one example, TBS is UE specific. The TBS fieldis configurable. One indication in the TBS field may correspond todifferent configurations for different UEs. The table below illustratesan example of TBS that may be used in an explicit field of a DCItransmitted to UEs. Two UEs are considered and both receive the sameDCI. The TBS field is three bits in length as shown in the first column.The first UE, UE1, supports one TBS only whereas the second UE, UE 2,supports two TBS. Modulation and resource allocations for a first TBSare identified in rows 2 to 5 of the third column and modulation andresource allocations for a second TBS are identified in rows 6 to 9 ofthe third column. Different bitmaps in the TBS field correspond todifferent resource allocations corresponding to the TBS size supportedby a UE. There can be a separate field to indicate starting RB index.

TABLE 9 Example of TBS bitmaps TBS field UE 1 (supports UE 2 (supports(3 bits) one TBS) two TBS) 000 MCS1a, RB Alloc 1a MCS2a, RB Alloc 2a 001MCS1b, RB Alloc 1b MCS2b, RB Alloc 2b {close oversize brace} TBS 1 010MCS1c, RB Alloc 1c MCS2c, RB Alloc 2c 011 MCS1d, RB Alloc 1d MCS2d, RBAlloc 2d 100 MCS1e, RB Alloc 1e MCS2e, RB Alloc 2e 101 MCS1f, RB Alloc1f MCS2f, RB Alloc 2f {close oversize brace} TBS 2 110 MCS1g, RB Alloc1g MCS2g, RB Alloc 2g 111 MCS1h, RB Alloc 1h MCS2h, RB Alloc 2h

In one example, if a UE support one TBS only, UE may be indicated MCSonly. Then, based on data duration, UE can identify how many REs or RBsare assigned. Starting RB index may be indicated.

In one example, RB allocation field indicates contiguous ornon-contiguous sub-carrier group which are used for data transmissionover the indicated duration. If only one TBS is supported, then MCSfield can be omitted as number of RBs assigned together with dataduration indicated can implicitly contain MCS information.

In another example, if UE supports M TBS, a field can be used toindicate a TBS index consisting of log₂M bits. Then number of RBsassigned together with data duration indicated would implicitly containMCS information for the indicated TBS index.

In another example, values of indicated MCS, indicated RBs orsub-carrier group, indicated data duration can be mapped to one or moreUE specific look-up tables to obtain TBS information.

For PDCCH re-transmissions that occur before data ACK/NACKs, the PDCCHcan also provide TBS information or resource assignment, or both.

In conventional protocols, such as LTE, it is assumed as indicated abovethat the UE knows the TBS information from initial transmission. Themodulation type can be provided in a reserved field with the resourceassignment.

According to embodiments of the present application, in particular inthe case of URLLC, the TBS information is provided explicitly inrepetitions subsequent to the first PDCCH, in case the UE missed firstPDCCH. In one example, as part of the TBS information, the new dataindicator (NDI) bit may or may not be toggled and a same HARQ processmay be identified. The UE can be configured to interpret the NDI fieldaccordingly.

If multiple PDCCH are received, i.e. the initial PDCCH and anysubsequent retransmissions, the UE can combine data from the multiplePDCCHs if that schedule same HARQ process data.

As mentioned above in respect to FIG. 36 , the second PDCCH can updatethe ACK/NACK timing.

For re-transmissions of the PDCCH after data ACK/NACK, the PDCCH mayprovide the modulation type and resource assignment only as the TBSshould have been successfully detected if data ACK/NACKS are being sent.

In some embodiments improved PDCCH reliability may be provided based onan increased level of diversity, for example the PDCCHs may be receivedin the same TTI with different antenna ports or different DMRSconfigurations in a same or different CORESETs. The PDCCH can betransmitted from the same TRP or multiple TRPs, subject to backhaullimitations, in a manner that is transparent to the UE.

Auxiliary Identities and Auxiliary Search Spaces

In some embodiments, a UE can be configured by the network with at leastone UE-specific configurable auxiliary identity. The signaling ofidentities to the UE can be done using higher-layer signaling (e.g. RRCsignaling), where primary identities and auxiliary identities areexplicitly signaled to the UE. The signaling of identities to the UE canalso be done in an implicit manner, for instance: a primary identity isdefined as an identity that is assigned as part of having completed therandom access procedure and an auxiliary identity is defined as anidentity that is assigned after the UE has already been assigned aprimary identity.

In some embodiments, a UE can be configured by the network with at leastone UE-specific configurable auxiliary identity for the purpose ofmonitoring at least one CORESET group for a particular UE-specificauxiliary search space. Each CORESET group for a particular UE-specificauxiliary search space can have a specific search space definitionincluding a specific aggregation level and/or a total number of decodingcandidates and/or time, frequency resources indexed by the UE-specificauxiliary identity. A representative example is shown in FIG. 37 . FIG.37 illustrates a first TRP1 3702 and a second TRP2 3704. FIG. 37 alsoillustrates a first UE1 3712, a second UE2 3713 and a third UE3 3714.The network configures UE1 3712 to monitor for a primary DL assignment3722 from TRP1 3702 and to monitor for an auxiliary DL assignment 3723from TRP2 3704. The network configures UE2 3713 to monitor for a primaryDL assignment 3724 from TRP2 3704 and to monitor for an auxiliary DLassignment 3725 from TRP1 3702. The network configures UE3 3714 tomonitor for a primary DL assignment 3726 from TRP2 3704 and for anauxiliary DL assignment 3727 from TRP1 3704.

In some embodiments, the network can configure some fields defined incontrol channel messages using higher-layer signaling (e.g. RRCsignaling). As a first example, the UE can be configured to receive somefields via higher-layer signaling (e.g. RRC signaling) and to over-rideany values that the UE finds in control channel messages for fieldsalready configured using such higher-layer signaling. As a secondexample, the UE can be configured to receive some fields viahigher-layer signaling (e.g. RRC signaling) and to receive other fieldsvia control channel messages.

In some embodiments, a UE can be configured by the network usinghigher-layer signaling (e.g. RRC signaling) to monitor for controlchannel messages on UE-specific auxiliary search spaces and to discardsome specific fields of the control channel message received overUE-specific auxiliary search spaces, such as (but not limited to) the ULSRS trigger, the CSI request or the QCL indication.

In some embodiments, a UE can be configured by the network usinghigher-layer signaling (e.g. RRC signaling) to monitor for controlchannel messages on UE-specific auxiliary search spaces with modifiedformats. As a first example, a UE can be configured to receive controlchannel messages with one or more fields have been removed such as (butnot limited to) the UL SRS trigger, the CSI request or the QCLindication. As a second example, the network can signal via higher-layersignaling (e.g. RRC signaling) which fields are to be configureddynamically in a control channel message and which fields are to beconfigured semi-statically using higher-layer signaling. As a thirdexample, the UE can be configured to receive control channel messageswith a new field whose definition and value can be signaled to the UEvia higher-layer signaling (e.g. RRC signaling), where the new field canbe located on one or more existing field(s) or on reserved bits/fieldsthat are present in a control channel message for other undefined usageor on a new location where no fields were previously defined. As afourth example, the UE can be configured to receive control channelmessages with additional fields in newly defined locations, which can besignaled using higher-layer signaling (e.g. RRC signaling).

In some embodiments, the network can transmit at least one controlchannel message on UE-specific auxiliary search spaces where the controlchannel message is appended with a CRC scrambled with a UE-specificprimary identity (e.g. C-RNTI) or with a UE-specific auxiliary identity.

In some embodiments, the network can transmit at least two controlchannel messages within the same CORESET on overlapping UE-specificsearch spaces where at least one search space is indicated using aprimary identity (e.g. C-RNTI) and at least one search space isindicated using an auxiliary identity. The UE can either separate thecontrol channel messages using the DMRS associated with a givenassignment or the network explicitly maps the modulated symbolscorresponding to the control channel messages on non-overlappingtime-frequency resources.

According to an aspect of the present disclosure there is provided amethod that includes: a first transmit receive point (TRP) transmittinga first transmission on a dynamically scheduled resource; and in a sametime resource block, a second TRP transmitting a second transmission ona configured resource.

In some embodiments, the method further includes notifying a userequipment (UE) of the configured resource, wherein the UE receivesconfiguration of the resource set from higher layer or RRC signaling.

In some embodiments, the second transmission on the configured resourceis the same as the first transmission on the dynamically scheduledresource.

In some embodiments, the second transmission and the first transmissionbelong to the same HARQ process.

In some embodiments, notifying the UE of the configured resourcecomprises using semi-persistent scheduling (SPS).

In some embodiments, the method further includes the first TRPtransmitting an activation signal indicating that the configuredresource is available for use.

In some embodiments, the method further includes the first or second TRPtransmitting a de-activation signal indicating that the configuredresource is no longer available for use.

In some embodiments, during a handover from the first TPR to the secondTRP, the second transmission identifies the second TRP as a new servingTRP and in a subsequent time resource block; the second TRP transmittingon a dynamically scheduled resource; and in the same subsequent timeresource block, the first TRP transmitting on the configured resource.

In some embodiments, transmitting the activation signal or thedeactivation signal includes transmitting at least one of: a userequipment (UE) downlink control information (DCI) message; a UE groupDCI message; a radio resource control (RRC) message; and a media accesscontrol control element (MAC-CE) message.

In some embodiments, transmitting an activation signal includesinformation identifying when to expect transmission over the configuredtime-frequency resource set from the second TRP.

In some embodiments, the second TRP stops ongoing transmission over theconfigured time-frequency resource to use it for transmission for the UEfor which the resource set is configured.

According to an aspect of the present disclosure there is provided amethod that includes: a first transmit receive point (TRP) transmittinga first transmission over a first time-frequency resource; and a secondTRP dynamically scheduling transmission for duplicated data over asecond time-frequency resource.

In some embodiments, the method further includes duplicating data by atleast one of: duplicating with different variations of protocol stacks;duplication at packet data convergence protocol (PDCP) layer;duplication at RLC layer; and duplication at media access layer (MAC)layer.

According to an aspect of the present disclosure there is provided amethod that includes: a central scheduler scheduling an initialtransmission and one or more re-transmissions from at least two transmitreceive points (TRP), wherein each of the at least two TRP transmits atleast one of the initial transmission and the one or morere-transmissions.

In some embodiments, scheduling an initial transmission and one or morere-transmissions includes, for a maximum of N re-transmissions, N beingan integer ≥1, scheduling at least the initial transmission and Kre-transmissions, K being an integer ≥0, from the first TRP and N-Ktransmissions from the second TRP.

In some embodiments, the method further includes transmittingquasi-co-location (QCL) information regarding one or more of the atleast two TRP in a DCI message.

According to an aspect of the present disclosure there is provided amethod that includes: a first transmit receive point (TRP) scheduling aninitial transmission and one or more re-transmissions from the first TRPand at least one second TRP; and the first TRP transmitting schedulinginformation to the at least one second TRP.

In some embodiments, the method further includes the second TRP updatingthe scheduling of re-transmissions from the second TRP.

According to an aspect of the present disclosure there is provided amethod that includes: a first transmit receive point (TRP) scheduling aninitial transmission and one or more re-transmissions from the first TRPand at least one second TRP; the first TRP transmitting schedulinginformation to the at least one second TRP; and the at least one secondTRP scheduling at least one re-transmission from the at least one secondTRP.

In some embodiments, the at least one second TRP scheduling at least onere-transmission from the at least one second TRP comprises the at leastone second TRP scheduling the at least one re-transmission based on thescheduling information received from the first TRP.

In some embodiments, the at least one second TRP scheduling at least onere-transmission from the at least one second TRP includes the at leastone second TRP scheduling the at least one re-transmission independentlyof the scheduling information received from the first TRP.

In some embodiments, the method further includes duplicating the initialtransmission by at least one of: duplicating with different variationsof protocol stacks; duplication at packet data convergence protocol(PDCP) layer; and duplication at media access layer (MAC) layer.

According to an aspect of the present disclosure there is provided amethod that includes: scheduling at least two uplink control channelsfor transmission of the same data, the data on each channel of the atleast two channels having the same hybrid automatic request (HARQ)process identifier (ID).

According to an aspect of the present disclosure there is provided amethod that includes: scheduling at least two uplink control channelsfor transmission of different data, the data on each channel of the atleast two channels having the same hybrid automatic request (HARQ)process identifier (ID).

In some embodiments, the method further includes a downlink controlchannel indicating a number N, N being an integer 1, of resources for Nrepetitions for each of the at least two uplink control channels.

In some embodiments, the method further includes configuring a userequipment (UE) with a number N, N being an integer 1, of repetitions forthe uplink control channel.

In some embodiments, based on the transmission resources assigned forthe at least two uplink control channels, the repetition follows ahopping pattern.

Although a combination of features is shown in the illustratedembodiments, not all of them need to be combined to realize the benefitsof various embodiments of this disclosure. Moreover, selected featuresof one example embodiment may be combined with selected features ofother example embodiments.

While this disclosure has been described with reference to illustrativeembodiments, this description is not intended to be construed in alimiting sense. Various modifications and combinations of theillustrative embodiments, as well as other embodiments of thedisclosure, will be apparent to persons skilled in the art uponreference to the description. It is therefore intended that the appendedclaims encompass any such modifications or embodiments.

Although the present disclosure describes methods and processes withsteps in a certain order, one or more steps of the methods and processesmay be omitted or altered as appropriate. One or more steps may takeplace in an order other than that in which they are described, asappropriate.

While the present application is described, at least in part, in termsof methods, a person of ordinary skill in the art will understand thatthe present disclosure is also directed to the various components forperforming at least some of the aspects and features of the describedmethods, be it by way of hardware components, software or anycombination of the two. Accordingly, the technical solution described inthe present disclosure may be embodied in the form of a softwareproduct. A suitable software product may be stored in a pre-recordedstorage device or other similar non-volatile or non-transitory computerreadable medium, including DVDs, CD-ROMs, USB flash disk, a removablehard disk, or other storage media, for example. The software productincludes instructions tangibly stored thereon that enable a processingdevice (e.g., a personal computer, a server, or a network device) toexecute embodiments of the methods disclosed herein.

The teachings of the present application may be embodied in otherspecific forms without departing from the subject matter of the claims.The described example embodiments are to be considered in all respectsas being only illustrative and not restrictive. Selected features fromone or more of the above-described embodiments may be combined to createalternative embodiments not explicitly described, features suitable forsuch combinations being understood within the scope of this disclosure.

1. A non-transitory computer readable medium storing instructions, whenthe instructions executed by an apparatus, cause the apparatus toperform operations including: receiving a configuration; monitoring morethan one physical downlink control channel (PDCCH) in a single PDCCHmonitoring occasion based on the configuration, wherein the more thanone PDCCH schedules more than one overlapped physical downlink sharedchannel (PDSCH), or the more than one PDCCH schedules more than oneoverlapped physical uplink shared channel (PUSCH), and wherein the morethan one PDCCH is associated with a radio network temporary identifier(RNTI); and receiving the more than one overlapped PDSCH in accordancewith the more than one PDCCH when scheduling the more than oneoverlapped PDSCH, or transmitting the more than one overlapped PUSCH inaccordance with the more than one PDCCH when scheduling the more thanone overlapped PUSCH.
 2. The non-transitory computer readable medium ofclaim 1, the more than one PDCCH scheduling the more than one overlappedPDSCH overlapping in frequency or in time.
 3. The non-transitorycomputer readable medium of claim 1, the operations further comprising:receiving a radio resource control (RRC) signaling indicating a physicaluplink control channel (PUCCH) feedback mode, wherein the PUCCH feedbackmode comprises a single PUCCH feedback for the more than one PDCCH, ormultiple PUCCHs feedback for the more than one PDCCH.
 4. Thenon-transitory computer readable medium of claim 1, the operationsfurther comprising: transmitting multiple PUCCHs, wherein each PUCCH ofthe multiple PUCCHs is associated with a different PDCCH of the morethan one PDCCH; or transmitting a single PUCCH by combiningacknowledgment (ACK)/negative acknowledgment (NACK) bits associated withthe more than one PDCCH.
 5. The non-transitory computer readable mediumof claim 4, wherein: for the single PUCCH, the ACK/NACK bits areconcatenated based on at least one of ordering and mapping rules: forthe ACK/NACK bits corresponding to different PDCCHs of the more than onePDCCH, first ACK/NACK bits corresponding to a first PDCCH with a lowerPDCCH index precede second ACK/NACK bits corresponding to a second PDCCHwith a higher PDCCH index, for the ACK/NACK bits corresponding to onePDCCH of the more than one PDCCH, first ACK/NACK bits corresponding to afirst codeword (CW) with a lower CW index precede second ACK/NACK bitscorresponding to a second CW with a higher CW index, or for the ACK/NACKbits corresponding to one CW, first ACK/NACK bits corresponding to afirst CB or a first CBG with a lower index precede second ACK/NACK bitscorresponding to a second CB or a second CBG with a higher index.
 6. Thenon-transitory computer readable medium of claim 4, wherein the multiplePUCCHs are transmitted within a slot.
 7. The non-transitory computerreadable medium of claim 6, wherein the multiple PUCCHs do not overlapin time, and wherein a starting orthogonal frequency-divisionmultiplexing (OFDM) symbol of each PUCCH of the multiple PUCCHs islocated within the slot, and wherein a duration of the each PUCCH isless than a slot duration of the slot.
 8. The non-transitory computerreadable medium of claim 1, wherein the more than one PDCCH isassociated with one serving cell.
 9. The non-transitory computerreadable medium of claim 1, the operations further comprising: obtainingan association between the more than one PDCCH and more than one controlresource set (CORESET); and monitoring a first PDCCH from a firstCORESET group and a second PDCCH from a second CORESET group based onthe association between the more than one PDCCH and the more than oneCORESET, wherein the first CORESET group includes first at least oneCORESET, and the second CORESET group includes second at least oneCORESET.
 10. The non-transitory computer readable medium of claim 9,wherein the obtaining the association further comprises: receiving morethan one CORESET configuration for the more than one CORESET, eachCORESET configuration of the more than one CORESET configurationindicating one identity associated with one of the more than one PDCCH,wherein at least two CORESET configurations of the more than one CORESETconfiguration indicate different identities.
 11. A non-transitorycomputer readable medium storing instructions, when the instructionsexecuted by a base station, cause the base station to perform operationsincluding: transmitting a configuration for a user equipment (UE) tomonitor more than one physical downlink control channel (PDCCH) in asingle PDCCH monitoring occasion, wherein the more than one PDCCHschedules more than one overlapped physical downlink shared channel(PDSCH), or the more than one PDCCH schedules more than one overlappedphysical uplink shared channel (PUSCH), and wherein the more than onePDCCH is associated with a radio network temporary identifier (RNTI);and transmitting the more than one overlapped PDSCH in accordance withthe more than one PDCCH when scheduling the more than one overlappedPDSCH, or receiving the more than one overlapped PUSCH in accordancewith the more than one PDCCH when scheduling the more than oneoverlapped PUSCH.
 12. The non-transitory computer readable medium ofclaim 11, the operations further comprising: transmitting a radioresource control (RRC) signaling indicating a physical uplink controlchannel (PUCCH) feedback mode, wherein the PUCCH feedback mode comprisesa single PUCCH feedback for the more than one PDCCH, or multiple PUCCHsfeedback for the more than one PDCCH.
 13. The non-transitory computerreadable medium of claim 11, the operations further comprising:receiving multiple PUCCHs, wherein each PUCCH of the multiple PUCCHs isassociated with a different PDCCH of the more than one PDCCH; orreceiving a single PUCCH by combining acknowledgment (ACK)/negativeacknowledgment (NACK) bits associated with the more than one PDCCH. 14.The non-transitory computer readable medium of claim 13, wherein: forthe single PUCCH, the ACK/NACK bits are concatenated based on at leastone of ordering and mapping rules: for the ACK/NACK bits correspondingto different PDCCHs of the more than one PDCCH, first ACK/NACK bitscorresponding to a first PDCCH with a lower PDCCH index precede secondACK/NACK bits corresponding to a second PDCCH with a higher PDCCH index,for the ACK/NACK bits corresponding to one PDCCH of the more than onePDCCH, first ACK/NACK bits corresponding to a first codeword (CW) with alower CW index precede second ACK/NACK bits corresponding to a second CWwith a higher CW index, or for the ACK/NACK bits corresponding to oneCW, first ACK/NACK bits corresponding to a first CB or a first CBG witha lower index precede second ACK/NACK bits corresponding to a second CBor a second CBG with a higher index.
 15. The non-transitory computerreadable medium of claim 13, wherein the multiple PUCCHs are receivedwithin a slot.
 16. The non-transitory computer readable medium of claim11, wherein the more than one PDCCH is associated with one serving cell.17. An apparatus, comprising: at least one processor coupled with anon-transitory computer readable medium storing instructions, when theinstructions executed by the apparatus, cause the apparatus to performoperations including: receiving a configuration; monitoring more thanone physical downlink control channel (PDCCH) in a single PDCCHmonitoring occasion based on the configuration, wherein the more thanone PDCCH schedules more than one overlapped physical downlink sharedchannel (PDSCH), or the more than one PDCCH schedules more than oneoverlapped physical uplink shared channel (PUSCH), and wherein the morethan one PDCCH is associated with a radio network temporary identifier(RNTI); and receiving the more than one overlapped PDSCH in accordancewith the more than one PDCCH when scheduling the more than oneoverlapped PDSCH, or transmitting the more than one overlapped PUSCH inaccordance with the more than one PDCCH when scheduling the more thanone overlapped PUSCH.
 18. The apparatus of claim 17, the more than onePDCCH scheduling the more than one overlapped PDSCH overlapping infrequency or in time.
 19. The apparatus of claim 17, the operationsfurther comprising: receiving a radio resource control (RRC) signalingindicating a physical uplink control channel (PUCCH) feedback mode,wherein the PUCCH feedback mode comprises a single PUCCH feedback forthe more than one PDCCH, or multiple PUCCHs feedback for the more thanone PDCCH.
 20. The apparatus of claim 17, the operations furthercomprising: transmitting multiple PUCCHs, wherein each PUCCH of themultiple PUCCHs is associated with a different PDCCH of the more thanone PDCCH; or transmitting a single PUCCH by combining acknowledgment(ACK)/negative acknowledgment (NACK) bits associated with the more thanone PDCCH.